From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id CE29A12A8 for ; Sat, 28 Jan 2017 01:07:52 +0100 (CET) Received: by mail-pf0-f179.google.com with SMTP id e4so76301805pfg.1 for ; Fri, 27 Jan 2017 16:07:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=CaJiBDIisVHtuAR8juozaexPhKZ+kO2Yfvtk3kpaLj0=; b=NUA7ErNqb54/pC+KLBw2MCMza3o1GrynvlS6BLQ5ehNNdc82awHUN5vLbEvsEj0Z8H pXsOGZz37UQd7FKV1yGfNu2nI1om6eLy1cl1njLdGhu+lHclhJbw5Pk0fzAp2RLEjN6w pvesxZSNry9MAiVaKRS2KUjI7XatL3Vnq4DuIo7F8vOSqEuDGj4TNIVOYcwsiZnTulir I1nmlj75pKiAoTo+8esJl1kwq1vRQ+rBCQy8WrmfXPa33rcPEdGBvLVjeITTr7ivsx6A y0B9+lkGudXpsvEM3MpOJW8pOusEFCpdl1UUZpSZ9cG2oZXF/ddf1uqHqurHT49frD8u M0+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=CaJiBDIisVHtuAR8juozaexPhKZ+kO2Yfvtk3kpaLj0=; b=UMJfimcr5ViQ2lvdBDZmP+YFlR+JemmXWOFgGuYcqrOYYohvTSypxNrzhg7lLN8jD5 /010NltlN+eKLssjVLunAa8gTlkXj5TvomZXYuYTWVYi1zQYj9S12CpX+oDl/h3Ts1e2 FW04HrGQoh7x4CjO6QTEPPQ5I+n11js7XD2Ua71Q0hXa1l3o5v8LdFlgOBFBhx+8chwe Q45zFtMt0917Nwxt4N/N5T15h+8PwzxuNVeLzlJURDx6Vk29A9lufIhsuJIXaXPFlBzo 1li93F5mpoZ94k5zWM3acEHEypQLoFQSTeBbsvdoX/J6S8d7O6r7dYCFe2G5jmdfNvtR Rl/A== X-Gm-Message-State: AIkVDXJ9hi1FmdQLFpWUFjeV1eis/DAfkJlhl38f6f3VpAgMY4rRqL/wvjzWWl8h6Ii0RA== X-Received: by 10.98.7.11 with SMTP id b11mr11731290pfd.154.1485562072144; Fri, 27 Jan 2017 16:07:52 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id d78sm13891932pfb.43.2017.01.27.16.07.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 27 Jan 2017 16:07:51 -0800 (PST) Date: Fri, 27 Jan 2017 16:07:44 -0800 From: Stephen Hemminger To: Rob Zimmerman Cc: users@dpdk.org Message-ID: <20170127160744.5d21ad59@xeon-e3> In-Reply-To: References: <20170127140308.3855cbd2@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] RSS RETA size of 0 on vmxnet3? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2017 00:07:53 -0000 On Fri, 27 Jan 2017 18:21:10 -0500 Rob Zimmerman wrote: > Thanks for the reply, @networkplumber :) > > No KNI interface here, unfortunately. Just a plain-ol DPDK ethernet device. > > > In the scenario where the RETA size is 0 I'm using the vmxnet3_pmd. Within > the application the eth devices are initialized and I make a call to > rte_eth_dev_info_get(). > > What is everyone else seeing for the RETA size using vmxnet3? > > Thanks again everyone, > ~Rob It is a vmxnet3 missing feature. The VMXNET3 protocol has ability to get/set RSS table but the VMXNET3 driver in DPDK (originally by Intel) is missing that feature. Would not be hard to write, just look at Linux for protocol.