From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "kernel list" <linux-kernel@vger.kernel.org>,
rminnich@lanl.gov, lucho@ionkov.net,
v9fs-developer@lists.sourceforge.net
Subject: Re: Plan 9 Resource Sharing Support - what is it?
Date: Mon, 23 Jul 2007 11:37:41 -0500 [thread overview]
Message-ID: <a4e6962a0707230937vc5b23bg93e8b5b7f700aa3e@mail.gmail.com> (raw)
In-Reply-To: <20070723075434.GA9162@elf.ucw.cz>
On 7/23/07, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> What is "plan 9 resource sharing"? Some kind of mosix-like process
> migration? Could you explain it in two lines in Kconfig?
>
> http://v9fs.sf.net
>
> is redirect to
>
> http://v9fs.sourceforge.net/
>
> which tells me
>
> Moved to SWiK
>
> after clicking on that, I get to page with content, but no
> explanation (could Kconfig/MAINTAINERS be updated?).
>
Sure, I'll try to put something in that is considerably less vague and
I'll update the URLs as well. We've been somewhat lagging on
documentation. The most complete explanation is available in the
Freenix paper:
http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html
The short answer is that it is a Linux client for sharing file
systems, devices, and system services mapped as synthetic file systems
via a simple protocol. Its primary focus has been to keep things
simple, and to try and maintain support for being able to effectively
share synthetic file systems (like /proc, or /sysfs, or ones exported
by Plan 9 applications (Russ Cox's Plan 9 ports package contains a set
of Plan 9 applications ported to UNIX such as the Venti content
addressable storage system)).
Its being used internally by (at the very least) IBM Research and Los
Alamos National Labs. To date we've been focused on the client and a
few specialized servers, we are currently broadening our approach to a
better general-purpose server and evaluating if it makes sense to make
an in-kernel server available. We've also been looking at using 9p in
the context of virtualized environments to provide file service, and
perhaps sharing of other system resources as well. Once we have a
better handle on the server story, we'll produce a much larger body of
documentation discussing usage as well as development of 9p file
servers.
There are also side-efforts underway evaluating different methods of
extended the 9p protocol to better support the Linux (and other UNIX)
environments -- ideally without adding a signifigant amount of
complexity.
-eric
prev parent reply other threads:[~2007-07-23 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 7:54 Pavel Machek
2007-07-23 16:15 ` Al Viro
2007-07-23 16:39 ` Miklos Szeredi
2007-07-23 16:37 ` Eric Van Hensbergen [this message]
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=a4e6962a0707230937vc5b23bg93e8b5b7f700aa3e@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=pavel@ucw.cz \
--cc=rminnich@lanl.gov \
--cc=v9fs-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®