[PATCH v2 0/3] nvmet-rdma: SRQ per completion vector

Sagi Grimberg sagi at grimberg.me
Thu Nov 16 10:36:33 PST 2017


> Since there is an active discussion regarding the CQ pool architecture, I decided to push
> this feature (maybe it can be pushed before CQ pool).
> 
> This is a new feature for NVMEoF RDMA target,

Any chance having this for the rest? isert, srpt, svcrdma?

> results:
> 
> BS    1.read (target CPU)   2.read (target CPU)    3.read (target CPU)   4.read (target CPU)
> ---  --------------------- --------------------- --------------------- ----------------------
> 1k     5.88M (80%)            5.45M (72%)            6.77M (91%)          2.2M (72%)
> 
> 2k     3.56M (65%)            3.45M (59%)            3.72M (64%)          2.12M (59%)
> 
> 4k     1.8M (33%)             1.87M (32%)            1.88M (32%)          1.59M (34%)

I'm blown by the fact that there is such a small difference for 4k
reads, how many cpu-cores did you have on the target-system? single
numa-node? Maybe if that is the case we can use less srqs than 
per-completion-vector...



More information about the Linux-nvme mailing list