From: Stephen Hemminger <stephen@networkplumber.org>
To: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] RSS : All fragments to same Recv queue
Date: Wed, 8 Mar 2017 18:18:56 -0800 [thread overview]
Message-ID: <20170308181856.43e59d65@xeon-e3> (raw)
In-Reply-To: <CAGSp03nWpAQ7RG9zD5WRXHfe5RpLv=3Kx1VtSknqxBV4kDkNnQ@mail.gmail.com>
On Wed, 8 Mar 2017 21:20:57 +0530
Shyam Shrivastav <shrivastav.shyam@gmail.com> wrote:
> Hi
>
> We want to use RSS supported by intel 82599 NIC, with one lcore running on
> each processor and handling one receive queue. All fragments of an ipv4
> packet need to go to same receive queue and handled by same lcore for
> lockless reassembly. Looks like Intel 82599 supports RSS IPv4 hashing
> using just source and dest address fields and that should put all fragments
> on same queue ( can be enabled by ETH_RSS_IPV4 in rte_eth_rss_conf->rs_hf).
> Please let me know whether my understanding is correct.
>
> Thanks
> Shyam
Yes as long as you keep port numbers out of the RSS hash it should work,
but you may have to deal with fragments arriving over different paths.
There is nothing in IP architecture that prevents multi-pathing.
next prev parent reply other threads:[~2017-03-09 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 15:50 Shyam Shrivastav
2017-03-09 2:18 ` Stephen Hemminger [this message]
2017-03-09 4:55 ` Shyam Shrivastav
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=20170308181856.43e59d65@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=shrivastav.shyam@gmail.com \
--cc=users@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).