Re: [PATCH] nvme/tcp: Add support to set the tcp worker cpu affinity

[Sagi Grimberg]

> > > Not saying that this should be a solution though.
> > >
> > > How many queues does your controller support that you happen to use
> > > queue 0 ?
> > Our controller only support one io queue currently.
>
> Ouch.
> Remember, NVMe gets most of the performance improvements by using 
> several queues, and be able to bind the queues to cpu sets.
> Exposing just one queue will be invalidating any assumptions we do,
> and trying to improve interrupt steering won't work anyway.
>
> I sincerely doubt we should try to 'optimize' for this rather peculiar 
> setup.

I tend to agree. This is not a common setup that I'm particularly
interested in exporting something dedicated in the driver for fiddling
with it...