From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] net: Add function to get SW rxhash
Date: Tue, 24 Sep 2013 17:17:37 -0700 [thread overview]
Message-ID: <1380068257.3165.130.camel@edumazet-glaptop> (raw)
In-Reply-To: <CA+mtBx94yRWRNkfcbkOmFhMcspdyb-Q=jn0=dkAVTZrj-XFCDQ@mail.gmail.com>
On Tue, 2013-09-24 at 15:16 -0700, Tom Herbert wrote:
> If it's a big win for conntrack to process packets on same CPUs for
> both directions, we should program the RFS table to accomplish that.
conntrack uses no userland code, no user thread, so what are you going
to put in RFS table ?
Right now, RPS can be used for proper steering, you only have to
"ethtool -K eth{x} rxhash off"
[ Of course, this is becoming less a concern with multiqueue nics ]
prev parent reply other threads:[~2013-09-25 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 20:42 [PATCH 1/2 v2] net: Add function to get SW rxhash Tom Herbert
2013-09-24 21:30 ` Eric Dumazet
2013-09-24 22:16 ` Tom Herbert
2013-09-25 0:17 ` Eric Dumazet [this message]
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=1380068257.3165.130.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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