From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: i40e and RSS woes Date: Thu, 19 Feb 2015 16:50:10 +0200 Message-ID: <20150219145010.GB29513@cloudius-systems.com> References: <20150216133654.GQ24740@cloudius-systems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: dev-VfR2kkLFssw@public.gmane.org Return-path: Content-Disposition: inline In-Reply-To: <20150216133654.GQ24740-RmZWMc9puTNJc61us3aD9laTQe2KTcn/@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" CCing i40e driver author in a hope to get an answer. On Mon, Feb 16, 2015 at 03:36:54PM +0200, Gleb Natapov wrote: > I have an application that works reasonably well with ixgbe driver, but > when I try to use it with i40e I encounter various RSS related issues. > > First one is that for some reason i40e, when it builds default reta > table, round down number of queues to power of two. Why is this? If I > configure reta by my own using all of the queues everything seams to be > working. To add insult to injury I do not get any errors during > configuration some queues just do not receive any traffic. > > The second problem is that for some reason i40e does not use 40 byte > toeplitz hash key like any other driver, but it expects the key to be 52 > bytes. And it would have being fine (if we ignore the fact that it > contradicts MS spec), but how my high level code suppose to know that? > And again, device configuration does not fail when wrong key length is > provided, it just uses some other key. Guys this kind of error handling > is completely unacceptable. > > The last one is more of a question. Why interface to change RSS hash > function (XOR or toeplitz) is part of a filter configuration and not rss > config? > > -- > Gleb. -- Gleb.