Discussion:
nuke nfs over netiso?
(too old to reply)
Antti Kantee
2008-10-09 14:54:00 UTC
Permalink
Is anyone even dreaming of using nfs over ISO? I'm tempted to give it
the gentle treatment.
I don't think anybody is, but the code is minimal and it serves as an
example on how to write iso networking code.
I really don't think we should include a programming tutorial in a piece
of code which is complex enough already as is.

Eventually it would be nice to have NFS (server and client) as a module
and that means killing as much of #ifdef as possible. Yes, I know I
need to solve the same problem with INET vs. INET6, but I like to start
with the easy ones first.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
der Mouse
2008-10-09 16:37:01 UTC
Permalink
Post by Antti Kantee
Eventually it would be nice to have NFS (server and client) as a
module and that means killing as much of #ifdef as possible. Yes, I
know I need to solve the same problem with INET vs. INET6, but I like
to start with the easy ones first.
Actually, NFS can in principle run over any RPC transport. The only
way it's tied to addressing at all is the portmapper (and the legacy
hack that says NFS is at port 2049).

If we modularize NFS, we should do so in a way that abstracts away the
underlying transport, which would give us ISO/INET/INET6 ifdef
elimination for free.

/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML ***@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Thor Lancelot Simon
2008-10-09 16:56:58 UTC
Permalink
Post by der Mouse
Post by Antti Kantee
Eventually it would be nice to have NFS (server and client) as a
module and that means killing as much of #ifdef as possible. Yes, I
know I need to solve the same problem with INET vs. INET6, but I like
to start with the easy ones first.
Actually, NFS can in principle run over any RPC transport. The only
way it's tied to addressing at all is the portmapper (and the legacy
hack that says NFS is at port 2049).
If we modularize NFS, we should do so in a way that abstracts away the
underlying transport, which would give us ISO/INET/INET6 ifdef
elimination for free.
What he said.

The second copy of the metadata cache code is a nasty abstraction
violation too... just while we're making suggestions for the bored yet
avid.

Thor

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...