All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Dougall <davidd@et.byu.edu>
Cc: "pwitting@Cyveillance.com" <pwitting@cyveillance.com>,
	"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: RedHat 8.0 nfs
Date: 26 Mar 2003 00:19:18 +0100	[thread overview]
Message-ID: <shsr88v3uh5.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.51.0303251547190.3799@lewis.et.byu.edu>

>>>>> " " == David Dougall <davidd@et.byu.edu> writes:

     > This doesn't agree with what I have heard before.  I was always
     > told that this memory amount( 256k default) was shared by all
     > threads.  Therefore the more threads you had, the more

You were misinformed. In Linux 2.4.x, each RPC server thread allocates
a private buffer.

Cheers,
  Trond


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-03-25 23:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 18:42 RedHat 8.0 nfs pwitting
2003-03-25 22:50 ` David Dougall
2003-03-25 23:19   ` Trond Myklebust [this message]
2003-03-25 23:53   ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 18:34 pwitting
2003-03-26 23:43 ` Neil Brown
2003-03-25 23:27 pwitting
2003-03-20 16:52 pwitting
2003-03-20 20:28 ` Steve Dickson

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=shsr88v3uh5.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davidd@et.byu.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=pwitting@cyveillance.com \
    /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.