linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: NeilBrown <neilb@suse.de>
Cc: trond.myklebust@hammerspace.com, anna@kernel.org,
	chuck.lever@oracle.com, jlayton@kernel.org, kolga@netapp.com,
	Dai.Ngo@oracle.com, tom@talpey.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Remove comment for sp_lock
Date: Fri, 26 Apr 2024 14:15:27 +0800	[thread overview]
Message-ID: <30ab2ca2-2eaa-3c11-c5ff-580230b4b84c@linux.dev> (raw)
In-Reply-To: <171410437515.7600.14267125361277447684@noble.neil.brown.name>

Hi Neil,

On 4/26/24 12:06, NeilBrown wrote:
> On Fri, 26 Apr 2024, Guoqing Jiang wrote:
>> It is obsolete since sp_lock was discarded in commit 580a25756a9f
>> ("SUNRPC: discard sp_lock").
>>
>> Signed-off-by: Guoqing Jiang <guoqing.jiang@linux.dev>
>> ---
>>   net/sunrpc/svc_xprt.c | 1 -
>>   1 file changed, 1 deletion(-)
>>
>> diff --git a/net/sunrpc/svc_xprt.c b/net/sunrpc/svc_xprt.c
>> index b4a85a227bd7..ec78c277a02e 100644
>> --- a/net/sunrpc/svc_xprt.c
>> +++ b/net/sunrpc/svc_xprt.c
>> @@ -46,7 +46,6 @@ static LIST_HEAD(svc_xprt_class_list);
>>   
>>   /* SMP locking strategy:
>>    *
>> - *	svc_pool->sp_lock protects most of the fields of that pool.
>>    *	svc_serv->sv_lock protects sv_tempsocks, sv_permsocks, sv_tmpcnt.
>>    *	when both need to be taken (rare), svc_serv->sv_lock is first.
>>    *	The "service mutex" protects svc_serv->sv_nrthread.
>
> I usually make an effort to find those sorts of things but I obviously
> missed it this time.
> Thanks.

I find it occasionally during investigate one nfs issue 😁.

> Reviewed-by: NeilBrown <neilb@suse.de>

Thanks for your review!

Guoqing

  reply	other threads:[~2024-04-26  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  3:47 [PATCH] SUNRPC: Remove comment for sp_lock Guoqing Jiang
2024-04-26  4:06 ` NeilBrown
2024-04-26  6:15   ` Guoqing Jiang [this message]
2024-04-26 13:02 ` Chuck Lever

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=30ab2ca2-2eaa-3c11-c5ff-580230b4b84c@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tom@talpey.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;
as well as URLs for NNTP newsgroup(s).