From: Greg Banks <gnb@melbourne.sgi.com>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: Re: [PATCH] SGI 905314 (1/2): make NFSSVC_MAXBLKSIZE dependon PAGE_SIZE
Date: Tue, 02 Dec 2003 11:26:12 +1100 [thread overview]
Message-ID: <3FCBDC24.291BB858@melbourne.sgi.com> (raw)
In-Reply-To: Pine.LNX.4.44.0312011235290.23297-100000@kenzo.iwr.uni-heidelberg.de
Bogdan Costescu wrote:
>
> On Mon, 1 Dec 2003, Greg Banks wrote:
>
> > It's not that simple; the ia64 port can be configured for 64K pages,
> > which would result in nfsd reporting 128K for wtmax on UDP.
>
> But allocating only 32K in this case means half a page... A waste.
The 2.4 code now does a kmalloc(NFSSVC_MAXBLKSIZE+1024), which
ends up allocating nearly twice as many pages as we need, so it's
already that wasteful now.
Besides machines with 64K pages are going to be wasting a lot
more RAM elsewhere.
> Then
> maybe TCP should get its own setting ?
I plan on later submitting a patch against 2.6 to do that.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-12-02 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 12:43 [PATCH] SGI 905314 (1/2): make NFSSVC_MAXBLKSIZE depend on PAGE_SIZE Greg Banks
2003-11-30 22:26 ` Neil Brown
2003-11-30 23:26 ` Greg Banks
2003-12-01 11:38 ` Bogdan Costescu
2003-12-02 0:26 ` Greg Banks [this message]
2003-12-02 11:26 ` Mailbox corruption on The NFS server Shivaji Navale
2003-12-02 18:51 ` Juri Haberland
2003-12-02 19:35 ` Trond Myklebust
2003-12-03 10:56 ` Shivaji Navale
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=3FCBDC24.291BB858@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=neilb@cse.unsw.edu.au \
--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.