Thread (8 messages) 8 messages, 3 authors, 2016-08-02
STALE3620d

Re: [PATCH v3] nvmet-rdma: Correctly handle RDMA device hot removal

From: Christoph Hellwig <hidden>
Date: 2016-08-01 15:50:54
Also in: linux-nvme

On Mon, Aug 01, 2016 at 02:30:37PM +0300, Sagi Grimberg wrote:
quoted
How is ->remove_port synchronized vs the RDMA/CM even handler?
Easy, it isn't :)

So we have three choices here:
1. Add a lock in nvmet_port that only rdma will use for now (don't like
it)
or
2. Add nvmet_rdma_port as nvmet_port->priv with a lock (don't like it)
or
3. take the global nvmet_config_sem (hate it)

Any preferences?
(4) use cmpxchg?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help