From: jgg@ziepe.ca (Jason Gunthorpe) Date: Mon, 13 Nov 2017 19:48:22 -0700 Subject: [PATCH v3 0/9] Introduce per-device completion queue pools In-Reply-To: <75a7cfe3-58e0-b416-0b5b-beba1e8207fd@grimberg.me> References: <20171108095742.25365-1-sagi@grimberg.me> <1510245771.2608.6.camel@wdc.com> <1510248716.2608.17.camel@wdc.com> <6af627c8-2814-d562-21a2-f10788e44458@grimberg.me> <20171113203444.GJ22610@ziepe.ca> <75a7cfe3-58e0-b416-0b5b-beba1e8207fd@grimberg.me> Message-ID: <20171114024822.GN22610@ziepe.ca> On Mon, Nov 13, 2017@10:48:32PM +0200, Sagi Grimberg wrote: > > >>But if that is not the case, maybe we may have less completion > >>aggragation per interrupt. > > > >It is too bad we can't re-size CQs.. Can we? > > I wish we could, but its an optional feature so I can't see how we can > use it. Well, it looks like mlx4/5 can do it, which covers a huge swath of deployed hardware.. I'd say make an optimal implementation using resize_cq and just a working implementation without it? The only way to encourage vendors to implement optional features is to actually use them in the OS... Jason