From: Matthew Wilcox <willy@infradead.org>
To: Thiago Becker <tbecker@redhat.com>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com,
trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
kolga@netapp.com, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH RFC v3 0/6] Intruduce nfsrahead
Date: Wed, 23 Mar 2022 21:32:14 +0000 [thread overview]
Message-ID: <YjuR3h6yDYLoEeum@casper.infradead.org> (raw)
In-Reply-To: <20220323201841.4166549-1-tbecker@redhat.com>
On Wed, Mar 23, 2022 at 05:18:35PM -0300, Thiago Becker wrote:
> Recent changes in the linux kernel caused NFS readahead to default to
> 128 from the previous default of 15 * rsize. This causes performance
> penalties to some read-heavy workloads, which can be fixed by
> tuning the readahead for that given mount.
Which recent changes? Something in NFS or something in the VFS/MM?
Did you even think about asking a wider audience than the NFS mailing
list? I only happened to notice this while I was looking for something
else, otherwise I would never have seen it. The responses from other
people to your patches were right; you're trying to do this all wrong.
Let's start out with a bug report instead of a solution. What changed
and when?
next parent reply other threads:[~2022-03-23 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220323201841.4166549-1-tbecker@redhat.com>
2022-03-23 21:32 ` Matthew Wilcox [this message]
2022-03-23 21:58 ` Trond Myklebust
2022-03-25 12:31 ` Thiago Becker
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=YjuR3h6yDYLoEeum@casper.infradead.org \
--to=willy@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=kolga@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=tbecker@redhat.com \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox