From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Christoph Hellwig" <hch@infradead.org>,
"Latchesar Ionkov" <lionkov@gmail.com>,
"Andrew Morton" <akpm@osdl.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"V9FS Developers" <v9fs-developer@lists.sourceforge.net>
Subject: Re: [V9fs-developer] [PATCH] 9p: create separate 9p client interface
Date: Mon, 30 Apr 2007 11:30:29 -0500 [thread overview]
Message-ID: <a4e6962a0704300930r7e048a48u7c312b14beefcffd@mail.gmail.com> (raw)
In-Reply-To: <20070430161318.GA29321@infradead.org>
On 4/30/07, Christoph Hellwig <hch@infradead.org> wrote:
> On Mon, Apr 30, 2007 at 09:32:41AM -0600, Latchesar Ionkov wrote:
> > Create a separate 9P client interface that can be used outside the VFS
> > layer. In addition to VFS, the new interface can be used to export the
> > authentication channel or from other interfaces.
>
> And what exact users would that be? We have a huge dislike for putting
> abstractions in just for the abstractions sake, so if you want this
> merged you'd better present a highly useful client to that interface.
>
I'll let Lucho give more details on his possible uses for such an
interface -- for my part we have been looking at doing in-kernel
servers for more efficient export of devices and system services (such
as the network stack). We've been using user space applications for
doing such sharing, but there are undesirable inefficiencies in such
an approach.
>>19 files changed, 1656 insertions(+), 1585 deletions(-)
I believe the log message was poorly worded, it was more of a
reorganization of the existing interface versus the creation of an
additional interface.
>
> Also the non-filesystem interface code shouldn't live in fs/ but
> rather in net/9p/
>
Which bits do you think are candidates for such a move? The transport
interfaces? (there are a few more in the wings to cover shared memory
transports for VMMs among other things) Should the protocol elements
move as well? -- that seems a bit fuzzier to me.
-eric
next prev parent reply other threads:[~2007-04-30 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:32 Latchesar Ionkov
2007-04-30 16:13 ` Christoph Hellwig
2007-04-30 16:30 ` Eric Van Hensbergen [this message]
2007-04-30 17:00 ` Latchesar Ionkov
2007-04-30 18:16 ` Jan Engelhardt
2007-04-30 18:22 ` Latchesar Ionkov
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=a4e6962a0704300930r7e048a48u7c312b14beefcffd@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionkov@gmail.com \
--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®