From: Olaf Kirch <okir@suse.de>
To: Murali Bashyam <mbcoder@gmail.com>
Cc: Peter Astrand <astrand@cendio.se>, nfs@lists.sourceforge.net
Subject: Re: Improving unfsd scalability
Date: Thu, 30 Nov 2006 19:13:09 +0100 [thread overview]
Message-ID: <20061130181308.GA12747@suse.de> (raw)
In-Reply-To: <9c8209a10611300958q7fd8bcb8u1001cc936062308b@mail.gmail.com>
On Thu, Nov 30, 2006 at 09:58:00AM -0800, Murali Bashyam wrote:
> So this version of unfsd would fork several processes and there would be
> some dispatching process to hand RPC requests to them? I assume these are
> not multiple daemons invoked from the shell. The unfsd version available for
> download seems to be strictly single process, and doesn't seem to be doing
> this.
Search for older suse nfs-server RPMs; that unfsd should have the
support.
And no, there's no dispatching. You start "rpc.nfsd 8" and that
will open a UDP and TCP socket on port 2049, then fork 7 children.
UDP requests are handled by whichever daemon wakes up first.
Same for incoming TCP connects; after the connection is established,
it is handled by one daemon.
> And what happens if multiple processes handle writes on behalf of different
> clients to the same file? I just want to make sure the 8 process server can
> handle what ever the clients do i.e lock, read, write etc. Presumably there
> are inefficiencies, of course such as independent file handle caches within
> each process and not much sharing between them.
unfsd doesn't do NFS file locking, but otherwise the file handle cache
is robust enough to handle even writes.
Anything multithreaded would require writing your own librpc.
There's no way you can make the current RPC code reasonably
efficient wrt multithreading.
I just wish people would leave this old code to Rot In Peace :)
Olaf
--
Walks like a duck. Quacks like a duck. Must be a chicken.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-11-30 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 6:54 Improving unfsd scalability Murali Bashyam
2006-11-30 10:00 ` Peter Astrand
2006-11-30 10:22 ` Olaf Kirch
2006-11-30 17:58 ` Murali Bashyam
2006-11-30 18:13 ` Olaf Kirch [this message]
2006-11-30 18:27 ` Peter Astrand
2006-11-30 20:01 ` Olaf Kirch
2006-12-01 11:41 ` Improving unfsd scalability: TI-RPC Tony Reix
2006-12-01 13:52 ` Peter Astrand
2006-12-04 8:51 ` Improving unfsd scalability: TI-RPC test suite Tony Reix
2006-12-01 16:50 ` Improving unfsd scalability: TI-RPC Steve Dickson
2006-11-30 18:03 ` Improving unfsd scalability Murali Bashyam
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=20061130181308.GA12747@suse.de \
--to=okir@suse.de \
--cc=astrand@cendio.se \
--cc=mbcoder@gmail.com \
--cc=nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.