From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jari Aalto <jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [BUG] enhancement - 5.1. Setting Block Size to Optimize Transfer Speeds
Date: Tue, 4 Aug 2009 12:45:57 -0400 [thread overview]
Message-ID: <20090804164557.GA19196@fieldses.org> (raw)
In-Reply-To: <871vnssjlk.fsf-S166JWPS1wRq3zrG9Zoazw@public.gmane.org>
On Mon, Aug 03, 2009 at 11:55:35PM +0300, Jari Aalto wrote:
>
> At page
>
> "5.1. Setting Block Size to Optimize Transfer Speeds"
> http://nfs.sourceforge.net/nfs-howto/ar01s05.html
>
> The text refers to 2.4 Kernels. Please update the page by providing
> information about range of rsize, wsize values in 2.6.x series.
I think that howto is unmaintained--I doubt that's the only thing out of
date. Volunteers to take it over welcomed. Or we could remove it, or
replace it by something different.
--b.
prev parent reply other threads:[~2009-08-04 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 20:55 [BUG] enhancement - 5.1. Setting Block Size to Optimize Transfer Speeds Jari Aalto
[not found] ` <871vnssjlk.fsf-S166JWPS1wRq3zrG9Zoazw@public.gmane.org>
2009-08-04 16:45 ` J. Bruce Fields [this message]
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=20090804164557.GA19196@fieldses.org \
--to=bfields@fieldses.org \
--cc=jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox