On 7/1/05, Miklos Szeredi <[email protected]> wrote:
> >
> > v9fs has a user-level server too. Maybe it has been used in FUSE-like
> > scenarios more than NFS.
We've really only dabbled with v9fs and user-level file services,
mostly through interacting with Plan 9 From User Space applications
(http://www.plan9.us) However, there are people actively improving
this area of functionality including providing an SDK to allow easy
creation of synthetic file systems. That being said, there are many
aspects of v9fs which have been written/re-written with the express
purpose of providing support for such synthetics.
>
> I think the p9 protocol is suffering from trying to be too generic.
> The FUSE kernel interface is probably slightly tied to the linux VFS,
> and would present problems if trying to port to other *NIX or god
> forbid some other OS family altogether.
>
I don't know where 9P "suffers" from being too generic, it's just
well-designed and has done a good job of keeping things simple --
something that the plethora of over designed, bloated interfaces of
today could learn from.
>
> > Plus NFS and v9fs work across the network...
>
> Yes. I consider that a drawback. FUSE does data transfer very
> efficiently (single copy), without the heavy network infrastructure
> being in the way.
>
I'll grant you this is something v9fs-2.0 suffers from, but its
something we are actively addressing in v9fs-2.1. We're working more
towards the implementation that is present in the Plan 9 kernel, where
the core efficiently multiplexes the requests either directly to local
servers (in Plan 9's case via function call APIs) or encapsulates them
for shipping across the network. The 9P interface is used for both,
it just has different embodiments depending on underlying transport.
That being said, I imagine the time spent context switching in and out
of the kernel dominates performance. With a proper mux there is no
reason why v9fs can't be made as efficient as FUSE - and that's what
we intend to demonstrate in v9fs-2.1. Plus, with v9fs you get the
benefit of being able to export your synthetic file systems over the
network with no additional copies.
Further, when you create an infrastructure which is meant to work over
a network, you take fewer things for granted -- which ultimately leads
to a more robust system capable of dealing with many of these
problems.
-eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|