From: Steve Dickson <SteveD@redhat.com>
To: Greg Banks <gnb@sgi.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH 2.4] (retry) increase NFSSVC_MAXBLKSIZE on large page machines
Date: Mon, 26 Jul 2004 13:35:03 -0400 [thread overview]
Message-ID: <410540C7.1050508@RedHat.com> (raw)
In-Reply-To: <20040726081439.GE17056@sgi.com>
Greg Banks wrote:
>I've been out of the loop for a few weeks now so I'm getting back
>in by sending and resending a bunch of patches.
>
>This one (for 2.4 only) was sent twice but has not yet appeared in
>Marcello's BK.
>
>http://marc.theaimsgroup.com/?l=linux-nfs&m=107002386729570&w=2
>http://marc.theaimsgroup.com/?l=linux-kernel&m=108391490102531&w=2
>
>This patch makes NFSSVC_MAXBLKSIZE depend on PAGE_SIZE so that machines
>with large page sizes can take advantage of that feature to serve NFS
>with larger blocksizes, increasing performance and avoiding a fallback
>to synchronous traffic between machines with page sizes greater than 8K.
>Also, documents the actual constraints on NFSSVC_MAXBLKSIZE.
>
>
I've had people ask about this as well.... It would be good if this made
in (imho)....
SteveD.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-07-26 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 8:14 [PATCH 2.4] (retry) increase NFSSVC_MAXBLKSIZE on large page machines Greg Banks
2004-07-26 17:35 ` Steve Dickson [this message]
2004-07-27 4:10 ` Neil Brown
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=410540C7.1050508@RedHat.com \
--to=steved@redhat.com \
--cc=gnb@sgi.com \
--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.