From: Sangjin Han <sangjin@eecs.berkeley.edu>
To: Daniel Kan <dan@nyansa.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Is it possible to get symmetric hash from RSS for a given flow
Date: Thu, 27 Feb 2014 16:24:44 -0800 [thread overview]
Message-ID: <CAPG33HQb7wQO7XUqTeVZq9iOf1gkP0EYnR4=fAz1Ub4JRXu6Ow@mail.gmail.com> (raw)
In-Reply-To: <D4721FD3-C27D-4B8F-9990-AED186050106@nyansa.com>
Hi,
This is exactly what you want:
http://www.ndsl.kaist.edu/~shinae/papers/TR-symRSS.pdf
Sangjin
On Thu, Feb 27, 2014 at 4:22 PM, Daniel Kan <dan@nyansa.com> wrote:
> Hi,
> It appears that the hash computed from RSS is unidirectional. Hence, for a 5-tuple flow, packet in one direction can be routed to a queue that may be different than packet in the other direction. I'm wondering if there is a configuration or mechanism to get a symmetric hash so that all packets for a given flow will be in the same queue. Thanks in advance.
>
> Dan
next prev parent reply other threads:[~2014-02-28 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 0:22 Daniel Kan
2014-02-28 0:24 ` Sangjin Han [this message]
2014-02-28 1:04 ` Daniel Kan
2014-02-28 1:08 ` Stefan Baranoff
2014-02-28 5:34 ` Daniel Kan
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='CAPG33HQb7wQO7XUqTeVZq9iOf1gkP0EYnR4=fAz1Ub4JRXu6Ow@mail.gmail.com' \
--to=sangjin@eecs.berkeley.edu \
--cc=dan@nyansa.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).