Re: [PATCH v3] nvmet-rdma: Correctly handle RDMA device hot removal
From: Sagi Grimberg <hidden>
Date: 2016-08-02 06:39:48
Also in:
linux-nvme
From: Sagi Grimberg <hidden>
Date: 2016-08-02 06:39:48
Also in:
linux-nvme
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? -- 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