From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] FreeBSD 9p work
Date: Fri, 13 Sep 2002 03:29:05 -0400 [thread overview]
Message-ID: <Pine.GSO.4.21.0209130301520.17064-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <e32d6696d0c3c06ab8c2718db9e15ab2@collyer.net>
On Thu, 12 Sep 2002, Geoff Collyer wrote:
> I say "NFS/vfs/vnode" because the edges of those things have always
> seemed blurry, but it's not essential to use NFS. Is the vnode or VFS
> machinery really not sufficiently general to handle file system
> protocols other than NFS?
VFS is kernel mechanism - think of it as an equivalent of chan.c and
friends. Filesystems provide methods; VFS calls them. And that's
normal function calls. It doesn't know anything about any protocols -
that stuff belongs to filesystem.
Notice that in Plan 9 _all_ userland filesystems are the same as far
as kernel is concerned - it's #m. devmnt.c is just one of the kernel
filesystems and the fact that its implementation of methods happens
to talk 9P is its private business. The rest of kernel doesn't know
or care about that.
To get 9P on FreeBSD you either need to provide a kernel filesystem
a-la devmnt.c or take existing kernel filesystem that would happen to
talk to userland and do protocol translation in userland. In either
variant VFS will call (kernel) filesystem methods; then filesystem
will either talk 9P directly or talk some other protocol and have
userland process translate it into 9P.
The former requires writing a kernel fs. The latter requires choosing
a protocol used by one of existing kernel filesystems and translating
between it and 9P. AFAICS that will be messy for all such protocols -
none of them matches 9P well enough.
next prev parent reply other threads:[~2002-09-13 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 6:41 Geoff Collyer
2002-09-13 7:29 ` Alexander Viro [this message]
2002-09-14 0:19 ` Ronald G Minnich
2002-09-13 9:41 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 8:44 nigel
2002-09-13 5:28 Geoff Collyer
2002-09-13 6:37 ` Alexander Viro
2002-09-13 4:07 anothy
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=Pine.GSO.4.21.0209130301520.17064-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).