netdev - Re: [PATCH iproute2-next v4 0/6] ip: nexthop: Support resilient groups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c24997ef-92cd-a7c8-3d6a-36334567b622@gmail.com>
Date:   Fri, 19 Mar 2021 09:07:15 -0600
From:   David Ahern <dsahern@...il.com>
To:     Petr Machata <petrm@...dia.com>, netdev@...r.kernel.org,
        stephen@...workplumber.org
Cc:     Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH iproute2-next v4 0/6] ip: nexthop: Support resilient
 groups

On 3/17/21 6:54 AM, Petr Machata wrote:
> Support for resilient next-hop groups was recently accepted to Linux
> kernel[1]. Resilient next-hop groups add a layer of indirection between the
> SKB hash and the next hop. Thus the hash is used to reference a hash table
> bucket, which is then used to reference a particular next hop. This allows
> the system more flexibility when assigning SKB hash space to next hops.
> Previously, each next hop had to be assigned a continuous range of SKB hash
> space. With a hash table as an intermediate layer, it is possible to
> reassign next hops with a hash table bucket granularity. In turn, this
> mends issues with traffic flow redirection resulting from next hop removal
> or adjustments in next-hop weights.
> 
> In this patch set, introduce support for resilient next-hop groups to
> iproute2.
> 

applied to iproute2-next. Thanks,