From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by dpdk.org (Postfix) with ESMTP id 4F202B5D6 for ; Mon, 16 Feb 2015 14:37:01 +0100 (CET) Received: by mail-wg0-f51.google.com with SMTP id y19so29405897wgg.10 for ; Mon, 16 Feb 2015 05:37:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-disposition; bh=5ghCJBkgS2bfkm6nQ1vAGhEaLPDncH4sl0TFHQkppg8=; b=iVKeRflXhaAUpNaYLBsNg7GB3zmY2b3fmhR8QREYsZeOGEGATLboVfX+JMI+ditOZk +tzYcKZVrwDDiD0syQgaGMZfEc+gAn+k0jqGEc6BUsmF8oExWpEglb8ZY7Z9w4XGxH2l 7NYJXLG8q8mgfPCYSO8CAqnhG4RZGmbrqD/XmGx3VBO98v8SjfVjCCf0gFPmMUztwNll zkqCwL/xF1KTXxv/dCps+zJtjt2yJqtMBuzwiO/MiCJJkf97TLcgfGSCIk12527waywS qhDdAnXildWZQYV9EED7kk0XnegOxS7aet9pv+UonfdVjtJNZtrTGbaOxsqg/chmSPh+ pQYQ== X-Gm-Message-State: ALoCoQnCF58OcRMvFQr17cahOmVFuHW0y/YXCkp4LohHqozOUj1wqhajQOmFxokG3JgBGZx3KXHh X-Received: by 10.194.90.210 with SMTP id by18mr48973619wjb.80.1424093821119; Mon, 16 Feb 2015 05:37:01 -0800 (PST) Received: from trex.cloudius-systems.com ([212.143.139.214]) by mx.google.com with ESMTPSA id y14sm9763101wjr.39.2015.02.16.05.36.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 05:37:00 -0800 (PST) Received: by trex.cloudius-systems.com (Postfix, from userid 1042) id 1910E83F85; Mon, 16 Feb 2015 15:36:54 +0200 (IST) Date: Mon, 16 Feb 2015 15:36:54 +0200 From: Gleb Natapov To: dev@dpdk.org Message-ID: <20150216133654.GQ24740@cloudius-systems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dpdk-dev] i40e and RSS woes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 13:37:01 -0000 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.