[PATCH WIP/RFC 6/6] nvme-rdma: keep a cm_id around during reconnect to get events

Christoph Hellwig hch at lst.de
Mon Aug 29 00:30:37 PDT 2016


On Sun, Aug 28, 2016 at 03:56:24PM +0300, Sagi Grimberg wrote:
> Care to respin your client registration patch so we can judge which
> is better?

FYI, I also really hate the idea of having to potentially allocate
resources on each device at driver load time which the client registration
forces us into.

I really think we need to take a step back and offer interfaces that don't
suck in the core instead of trying to work around RDMA/CM in the core.
Unfortunately I don't really know what it takes for that yet.  I'm pretty
busy this work, but I'd be happy to reserve a lot of time next week to
dig into it unless someone beats me.

I suspect a big part of that is having a queue state machine in the core,
and getting rid of that horrible RDMA/CM event multiplexer.



More information about the Linux-nvme mailing list