From: "Theodore Ts'o" <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] UniLinux -- Unikernelized Linux Exploration
Date: Thu, 30 May 2019 02:01:11 -0400 [thread overview]
Message-ID: <20190530060111.GA30403@mit.edu> (raw)
From: Tiejun Chen <tiejunc@vmware.com>
[ Note: The following abstract was submitted via the Linsux Plumbers
Conference website. Per the instructions that were posted for the
Maintainer's / Kernel Summit Call for Proposals[1], the proposal
should also be posted on the ksummit-discuss list, so that people
can comment on the proposal, and perhaps start a discussion before
the summit.
[1] https://lwn.net/Articles/788378/
Please note that topic proposals for both the Kernel Summit and the
Maintainer's Summit are still welcome, and the deadline has been
extended to June 3rd. -- Ted ]
Unikernel is relatively a novel software technology that links an
application with OS in the form of a library and packages them into a
specialized image that facilitates direct deployment on a
hypervisor. And the reality is that no matter what we are talking the
cloud infrastructure, or IoT edge systems, etc, we really need this
across a variety of areas, buy those existing unikernels have yet to
gain large popularity. So what if we can convert Linux to Unikernel or
Unikernel-like? Here I'll talk what challenges Unikernels are facing,
and discuss my proposal of if-how we could convert Linux as Unikernel
like to make all kernel and user stuff working only kernel mode, how
to manage interrupt, how to further reduce memory size and footprint,
how to improve IO performance with light weight network stack, should
we support multiple processes in some light weight ways, etc. These
problem could be addressed but also need to further discuss during
LPC.
In terms of UniLinux, IoT and Serverless could be a valuable candidate
to make Unikernel succeed. Meantime, it should be a potential vessel
by replacing container, because compared to traditional container,
Unikernel is small, fast and more secure as a lightweight VM. So it is
really worthy fitting Unilinux into a variety of areas like IoT,
Serverless and so on.
next reply other threads:[~2019-05-30 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 6:01 Theodore Ts'o [this message]
2019-05-30 13:54 ` [Ksummit-discuss] [TECH TOPIC] UniLinux -- Unikernelized Linux Exploration Theodore Ts'o
2019-06-13 2:36 ` Tiejun Chen
2019-06-13 19:53 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190530060111.GA30403@mit.edu \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).