From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org, roland@purestorage.com
Subject: Re: arp_hash
Date: Sun, 22 Mar 2015 19:53:15 -0400 (EDT) [thread overview]
Message-ID: <20150322.195315.643961269309745827.davem@davemloft.net> (raw)
In-Reply-To: <20150322234218.GA9243@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Mon, 23 Mar 2015 10:42:18 +1100
> On Sun, Mar 22, 2015 at 06:57:14PM -0400, David Miller wrote:
>> From: Herbert Xu <herbert@gondor.apana.org.au>
>> Date: Mon, 23 Mar 2015 08:34:08 +1100
>>
>> > So what scales we are talking about, twice, three times? Have you
>> > considered more modern hashes such as SipHash or SpookyHash
>> > (successor to jhash/lookup3 and supposedly faster)?
>>
>> I want it to be one cycle or two.
>>
>> Every single transmitted packet hits this hash demux.
>
> For hosts can we cache this? For routers I guess this is just
> the mummified remains of the route cache :)
We want no reference counting of the neighbour entries, that's one of
the main points of all this.
That way packets getting stuck do not run into the classic
dreaded "Neighbour table overflow", remember that?
THAT is what is attackable when people have /8 subnets and
someone just spam pings every host on that subnet.
That is a more serious exposure than this hashing issue.
At least with ref-less use, as we have now, we could trim hash chains
that get too large with almost no barriers whatsoever because nearly
every neigh entry has no external references outside of these demux
sequences.
next prev parent reply other threads:[~2015-03-22 23:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 11:42 arp_hash Herbert Xu
2015-03-22 12:56 ` arp_hash Eric Dumazet
2015-03-22 16:57 ` arp_hash David Miller
2015-03-22 21:21 ` arp_hash Herbert Xu
2015-03-22 21:56 ` arp_hash Herbert Xu
2015-03-22 22:51 ` arp_hash Herbert Xu
2015-03-22 23:22 ` arp_hash Herbert Xu
2015-03-22 23:35 ` arp_hash Herbert Xu
2015-03-23 10:58 ` arp_hash Herbert Xu
2015-03-22 22:58 ` arp_hash David Miller
2015-03-22 23:08 ` arp_hash Herbert Xu
2015-03-22 23:50 ` arp_hash David Miller
2015-03-22 23:53 ` arp_hash Herbert Xu
2015-03-22 16:54 ` arp_hash David Miller
2015-03-22 21:34 ` arp_hash Herbert Xu
2015-03-22 22:57 ` arp_hash David Miller
2015-03-22 23:42 ` arp_hash Herbert Xu
2015-03-22 23:53 ` David Miller [this message]
2015-03-23 11:01 ` arp_hash Herbert Xu
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=20150322.195315.643961269309745827.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=roland@purestorage.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