From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
Cc: netdev@vger.kernel.org, eric@regit.org, victor@inliniac.net
Subject: Re: [PATCH] packet: Use symmetric hash for PACKET_FANOUT_HASH.
Date: Fri, 01 Jul 2016 17:07:01 -0400 (EDT) [thread overview]
Message-ID: <20160701.170701.1456256736115514983.davem@davemloft.net> (raw)
In-Reply-To: <CALx6S34B33PUMfk4R662_WEjiafjheNbH=wH9r=QhYTK14nmqw@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 1 Jul 2016 13:52:58 -0700
> Why are symmetric hashes required?
Because they want load balancing, such that one flow only can overrun
one single socket not all of the ones in the fanout.
Every single user of AF_PACKET fanout wants this behavior.
next prev parent reply other threads:[~2016-07-01 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 20:08 [PATCH] packet: Use symmetric hash for PACKET_FANOUT_HASH David Miller
2016-07-01 20:52 ` Tom Herbert
2016-07-01 21:07 ` David Miller [this message]
2016-07-01 21:16 ` Tom Herbert
2016-07-02 20:38 ` David Miller
2016-07-04 8:41 ` Victor Julien
2016-07-04 9:29 ` Hannes Frederic Sowa
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=20160701.170701.1456256736115514983.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric@regit.org \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=victor@inliniac.net \
/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).