On 12/14/20 16:25, na...@jack.fr.eu.org wrote:
There are 3 kind of hashing algorithm
Four if you count the trails followed by runners drinking beer.
See on-on for instance.
The first one is used to check the sanity of input, against bit-swapping
error for instance
See CRC for instance
The
Sorry to have sent unedited mail.
On 2020/12/15 3:16, Lawrence Wobker wrote:
So I’d argue that the pedantic answer is “you need only as many bits
of entropy as your largest fan out” — meaning that 10 bits would
allow 1024-way ECMP. But I don’t think that’s what you were actually
after...
Thubert (pthubert) ; NANOG
Subject: Re: how many bits of entropy do we need for load balancing?
So I’d argue that the pedantic answer is “you need only as many bits of entropy
as your largest fan out” — meaning that 10 bits would allow 1024-way ECMP.
Most of the challenges I’ve seen
Hey,
On Tue, 15 Dec 2020 at 02:28, wrote:
> There are 3 kind of hashing algorithm
I'm sure there are a lot more. Like 'cryptographic' purposes are
ambiguous. Proving that content hasn't been changed requires hash to
be fast and HW friendly, using hash to protect password requires hash
to be
o/
Small of out topic
On 12/14/20 7:16 PM, Lawrence Wobker wrote:
A “perfect” balancing algorithm would be crypto grade hash generation
with a large output, and a true modulo operation to select which member
we use.
There are 3 kind of hashing algorithm
The first one is used to check the
On Mon, 14 Dec 2020 at 16:58, Pascal Thubert (pthubert) via NANOG
wrote:
> The IPv6 flow label is 20 bits but hardware implementations do their
> balancing only on a subset of that, e.g. 12 or 16 bits.
Why? I don't think it's fundamentally true. Even if we imagine your
instruction set reading
many bits of entropy do we need for load balancing?
So I’d argue that the pedantic answer is “you need only as many bits of entropy
as your largest fan out” — meaning that 10 bits would allow 1024-way ECMP.
Most of the challenges I’ve seen are not around how many bits you end up with,
but rather
Dear all:
How many bits of entropy do we need for (ECMP) load balancing in the core?
This question has kept coming up regularly in many discussions and drafts at
the IETF.
The IPv6 flow label is 20 bits but hardware implementations do their balancing
only on a subset of that, e.g. 12 or 16
8 matches
Mail list logo
