From: Alex Forster <alex@alexforster.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Flow Director Example?
Date: Fri, 29 Apr 2016 20:34:23 +0000 [thread overview]
Message-ID: <3135F0AC-65EF-45B0-8D05-1B2AB691FF1B@alexforster.com> (raw)
Hi guys, apologies if this is the wrong list, but the others look pretty bare.
We have a 32 core server that has two X520-QDA1's NICs with 2x10G ports plugged into each. I'm using 2016.1 (latest stable) with ixgbe 4.3.15 (latest stable). I'm setting up 8 RX queues per port, and I'd like Flow Director in signature mode (?) to place packets into queues based on a hash of destination IPv4 or IPv6 address. However, I can't figure out rte_fdir_conf, and despite a good amount of trial and error, each of my ports are still only using one of the RX queues I set up.
Would anyone be able to point me in the right direction here? Thanks in advance!
Alex Forster
next reply other threads:[~2016-04-29 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 20:34 Alex Forster [this message]
2016-05-02 5:38 ` Zhang, Helin
2016-05-02 15:28 ` Alex Forster
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=3135F0AC-65EF-45B0-8D05-1B2AB691FF1B@alexforster.com \
--to=alex@alexforster.com \
--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).