From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever <cel@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@kernel.org>,
linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH 2/2] NFSD: Add asynchronous write throttling support
Date: Wed, 7 Jan 2026 17:25:03 +0100 [thread overview]
Message-ID: <20260107162503.GA23222@lst.de> (raw)
In-Reply-To: <cc3a3e80-7b2b-4652-811b-c2a126daf9c7@kernel.org>
On Wed, Jan 07, 2026 at 09:42:58AM -0500, Chuck Lever wrote:
> I'm happy to run with this one and drop (or postpone) 1/2, if that is
> your assessment.
I don't really understand what exactly patch 1 is aiming for. Not
stalling nfsd threads when congested makes total sense on the other
hand.
next prev parent reply other threads:[~2026-01-07 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 14:11 [RFC PATCH 0/2] NFSD: Rate-limiting unstable WRITEs Chuck Lever
2025-12-19 14:11 ` [RFC PATCH 1/2] NFSD: Add aggressive write throttling control Chuck Lever
2026-01-07 7:55 ` Christoph Hellwig
2026-01-07 14:36 ` Chuck Lever
2026-01-07 14:42 ` Christoph Hellwig
2026-01-07 14:49 ` Chuck Lever
2025-12-19 14:11 ` [RFC PATCH 2/2] NFSD: Add asynchronous write throttling support Chuck Lever
2025-12-20 15:34 ` kernel test robot
2025-12-21 5:41 ` kernel test robot
2025-12-22 18:06 ` kernel test robot
2025-12-22 23:47 ` kernel test robot
2026-01-07 8:00 ` Christoph Hellwig
2026-01-07 14:42 ` Chuck Lever
2026-01-07 16:25 ` Christoph Hellwig [this message]
2026-01-07 19:40 ` Mike Snitzer
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=20260107162503.GA23222@lst.de \
--to=hch@lst.de \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@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 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.