DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: [dpdk-dev] Alternatives to RSS on virtio-net devices
Date: Tue, 14 Oct 2014 00:07:13 -0700	[thread overview]
Message-ID: <20141014070713.GA17384@mhcomputing.net> (raw)

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.

                 reply	other threads:[~2014-10-14  7:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141014070713.GA17384@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).