From: Chuck Lever III <chuck.lever@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: Jeff Layton <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] Revisions for topic-sunrpc-thread-scheduling
Date: Tue, 5 Sep 2023 18:10:10 +0000 [thread overview]
Message-ID: <0B88EBEB-48DB-4729-9FBC-7DD0F46FBEC2@oracle.com> (raw)
In-Reply-To: <20230905014011.25472-1-neilb@suse.de>
> On Sep 4, 2023, at 9:38 PM, NeilBrown <neilb@suse.de> wrote:
>
> This a resend of two recently sent patches (1 and 3) with
> review comments addressed, plus a new patch (2) which renames
> some function names for improved consistency.
>
> Thanks,
> NeilBrown
>
> [PATCH 1/3] lib: add light-weight queuing mechanism.
> [PATCH 2/3] SUNRPC: rename some functions from rqst_ to svc_thread_
> [PATCH 3/3] SUNRPC: only have one thread waking up at a time
Applied these and the remaining patches from the previous
series. No build problems with this set. I'll test them
for a bit and then post the latest version of the whole
series for further review.
--
Chuck Lever
next prev parent reply other threads:[~2023-09-05 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 1:38 [PATCH 0/3] Revisions for topic-sunrpc-thread-scheduling NeilBrown
2023-09-05 1:38 ` [PATCH 1/3] lib: add light-weight queuing mechanism NeilBrown
2023-09-05 1:38 ` [PATCH 2/3] SUNRPC: rename some functions from rqst_ to svc_thread_ NeilBrown
2023-09-05 1:38 ` [PATCH 3/3] SUNRPC: only have one thread waking up at a time NeilBrown
2023-09-05 18:10 ` Chuck Lever III [this message]
2023-09-05 21:04 ` [PATCH 0/3] Revisions for topic-sunrpc-thread-scheduling NeilBrown
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=0B88EBEB-48DB-4729-9FBC-7DD0F46FBEC2@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).