From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH 3/5] SUNRPC: Remove the bh-safe lock requirement on xprt->transport_lock
Date: Fri, 3 May 2019 11:43:40 -0400 [thread overview]
Message-ID: <250A97DF-6803-40FD-A432-B4AFF23B1D30@oracle.com> (raw)
In-Reply-To: <0fb44ee09e95964ab04c0b25470d871d43bf91b6.camel@gmail.com>
> On May 3, 2019, at 11:28 AM, Trond Myklebust <trondmy@gmail.com> wrote:
>
> On Fri, 2019-05-03 at 10:21 -0400, Chuck Lever wrote:
>>> On May 3, 2019, at 7:18 AM, Trond Myklebust <trondmy@gmail.com>
>>> wrote:
>>>
>>> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
>>> ---
>>> net/sunrpc/xprt.c | 61 ++++++++++---------
>>> ---
>>> net/sunrpc/xprtrdma/rpc_rdma.c | 4 +-
>>> net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 4 +-
>>> net/sunrpc/xprtrdma/svc_rdma_transport.c | 8 +--
>>> net/sunrpc/xprtsock.c | 23 ++++----
>>> 5 files changed, 47 insertions(+), 53 deletions(-)
>>
>> For rpc_rdma.c and svc_rdma_backchannel.c:
>>
>> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
>>
>> For svc_rdma_transport.c:
>>
>> These locks are server-side only. AFAICS it's not safe
>> to leave BH's enabled here. Can you drop these hunks?
>
> Oops... Yes, I don't know why I mistook that for the xprt-
>> transport_lock...
>
> You mean these 3 hunks, right?
Sí.
>
>>> diff --git a/net/sunrpc/xprtrdma/svc_rdma_transport.c
>>> b/net/sunrpc/xprtrdma/svc_rdma_transport.c
>>> index 027a3b07d329..18ffc6190ea9 100644
>>> --- a/net/sunrpc/xprtrdma/svc_rdma_transport.c
>>> +++ b/net/sunrpc/xprtrdma/svc_rdma_transport.c
>>> @@ -221,9 +221,9 @@ static void handle_connect_req(struct
>>> rdma_cm_id *new_cma_id,
>>> * Enqueue the new transport on the accept queue of the
>>> listening
>>> * transport
>>> */
>>> - spin_lock_bh(&listen_xprt->sc_lock);
>>> + spin_lock(&listen_xprt->sc_lock);
>>> list_add_tail(&newxprt->sc_accept_q, &listen_xprt-
>>>> sc_accept_q);
>>> - spin_unlock_bh(&listen_xprt->sc_lock);
>>> + spin_unlock(&listen_xprt->sc_lock);
>>>
>>> set_bit(XPT_CONN, &listen_xprt->sc_xprt.xpt_flags);
>>> svc_xprt_enqueue(&listen_xprt->sc_xprt);
>>> @@ -396,7 +396,7 @@ static struct svc_xprt *svc_rdma_accept(struct
>>> svc_xprt *xprt)
>>> listen_rdma = container_of(xprt, struct svcxprt_rdma, sc_xprt);
>>> clear_bit(XPT_CONN, &xprt->xpt_flags);
>>> /* Get the next entry off the accept list */
>>> - spin_lock_bh(&listen_rdma->sc_lock);
>>> + spin_lock(&listen_rdma->sc_lock);
>>> if (!list_empty(&listen_rdma->sc_accept_q)) {
>>> newxprt = list_entry(listen_rdma->sc_accept_q.next,
>>> struct svcxprt_rdma, sc_accept_q);
>>> @@ -404,7 +404,7 @@ static struct svc_xprt *svc_rdma_accept(struct
>>> svc_xprt *xprt)
>>> }
>>> if (!list_empty(&listen_rdma->sc_accept_q))
>>> set_bit(XPT_CONN, &listen_rdma->sc_xprt.xpt_flags);
>>> - spin_unlock_bh(&listen_rdma->sc_lock);
>>> + spin_unlock(&listen_rdma->sc_lock);
>>> if (!newxprt)
>>> return NULL;
>>>
>>>
>
> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
>
>
>
next prev parent reply other threads:[~2019-05-03 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 11:18 [RFC PATCH 0/5] bh-safe lock removal for SUNRPC Trond Myklebust
2019-05-03 11:18 ` [RFC PATCH 1/5] SUNRPC: Replace the queue timer with a delayed work function Trond Myklebust
2019-05-03 11:18 ` [RFC PATCH 2/5] SUNRPC: Replace direct task wakeups from softirq context Trond Myklebust
2019-05-03 11:18 ` [RFC PATCH 3/5] SUNRPC: Remove the bh-safe lock requirement on xprt->transport_lock Trond Myklebust
2019-05-03 11:18 ` [RFC PATCH 4/5] SUNRPC: Remove the bh-safe lock requirement on the rpc_wait_queue->lock Trond Myklebust
2019-05-03 11:18 ` [RFC PATCH 5/5] SUNRPC: Reduce the priority of the xprtiod queue Trond Myklebust
2019-05-06 20:41 ` Chuck Lever
2019-05-28 19:03 ` Chuck Lever
2019-05-28 19:33 ` Trond Myklebust
2019-05-28 19:52 ` Chuck Lever
2019-05-29 17:13 ` Chuck Lever
2019-05-28 20:10 ` Olga Kornievskaia
2019-05-29 18:38 ` Olga Kornievskaia
2019-05-29 18:45 ` Trond Myklebust
2019-05-03 14:21 ` [RFC PATCH 3/5] SUNRPC: Remove the bh-safe lock requirement on xprt->transport_lock Chuck Lever
2019-05-03 15:28 ` Trond Myklebust
2019-05-03 15:43 ` Chuck Lever [this message]
2019-05-06 18:22 ` [RFC PATCH 0/5] bh-safe lock removal for SUNRPC Chuck Lever
2019-05-06 18:37 ` Trond Myklebust
2019-05-06 20: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=250A97DF-6803-40FD-A432-B4AFF23B1D30@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.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).