From: Parav Pandit <parav@mellanox.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-next v1 0/4] Let IB core distribute cache update events
Date: Wed, 8 Jan 2020 11:42:32 +0000 [thread overview]
Message-ID: <d9572722-466d-eb60-716e-a4de27c618f3@mellanox.com> (raw)
In-Reply-To: <20200108002814.GA1937@ziepe.ca>
On 1/8/2020 5:58 AM, Jason Gunthorpe wrote:
> On Thu, Dec 12, 2019 at 01:30:20PM +0200, Leon Romanovsky wrote:
>
>> Parav Pandit (4):
>> IB/mlx5: Do reverse sequence during device removal
>> IB/core: Let IB core distribute cache update events
>> IB/core: Cut down single member ib_cache structure
>> IB/core: Prefix qp to event_handler_lock
>
> I used qp_open_list_lock in the last patch, and I'm still interested
> if/why globally serializing the qp handlers is required, or if that
> could be rw spinlock too.
>
My understanding is as in email of patch-2, its open_list_lock.
probably there isn't too much contention, but yes it can be changed to
rw spinlock.
> Otherwise applied to for-next
>
Thanks.
prev parent reply other threads:[~2020-01-08 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 11:30 [PATCH rdma-next v1 0/4] Let IB core distribute cache update events Leon Romanovsky
2019-12-12 11:30 ` [PATCH rdma-next v1 1/4] IB/mlx5: Do reverse sequence during device removal Leon Romanovsky
2019-12-12 11:30 ` [PATCH rdma-next v1 2/4] IB/core: Let IB core distribute cache update events Leon Romanovsky
2020-01-07 21:02 ` Jason Gunthorpe
2020-01-08 11:35 ` Parav Pandit
2019-12-12 11:30 ` [PATCH rdma-next v1 3/4] IB/core: Cut down single member ib_cache structure Leon Romanovsky
2019-12-12 11:30 ` [PATCH rdma-next v1 4/4] IB/core: Prefix qp to event_handler_lock Leon Romanovsky
2020-01-08 0:28 ` [PATCH rdma-next v1 0/4] Let IB core distribute cache update events Jason Gunthorpe
2020-01-08 11:42 ` Parav Pandit [this message]
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=d9572722-466d-eb60-716e-a4de27c618f3@mellanox.com \
--to=parav@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.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.