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

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

From: sagi@grimberg.me (Sagi Grimberg)
Date: 2016-08-02 06:39:48
Also in: linux-rdma

quoted
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?
I'm not exactly sure what you mean. Do you mean placing
cmpxchg in nvmet_rdma_device_removal()? To what we cmp
when we want to xchg?

Care to explain in a bit more detail?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help