From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id 514207E6A
 for <dev@dpdk.org>; Tue, 14 Oct 2014 09:00:19 +0200 (CEST)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 7744180C50B; Tue, 14 Oct 2014 00:07:13 -0700 (PDT)
Date: Tue, 14 Oct 2014 00:07:13 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Message-ID: <20141014070713.GA17384@mhcomputing.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: [dpdk-dev] Alternatives to RSS on virtio-net devices
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Oct 2014 07:00:19 -0000

Hello,

Having worked around the previously reported bizarre linker issues, I can now 
see this new error:

PMD: virtio_dev_start(): RSS cannot be configured for VirtI/O net devices

If I want to ensure that the flows are sent consistently to the same core on 
virtio-net to prevent surprises, what are my options?

Given these interfaces are probably slower than physical ones, is RX / TX from 
a single core a possibility? Distributor? What are people doing to get it to 
work? Is it better to use some other kind of interface like a fake virtual 
Intel NIC, where the RSS might be supported, instead?

Thanks,
Matthew.