netdev - Re: [PATCH RFC v2 net-next 00/21] net/ipv6: Separate data structures for FIB and data path

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] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 24 Mar 2018 09:28:01 -0600
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net,
        roopa@...ulusnetworks.com, eric.dumazet@...il.com,
        weiwan@...gle.com, kafai@...com, yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH RFC v2 net-next 00/21] net/ipv6: Separate data structures
 for FIB and data path

On 3/24/18 9:05 AM, Ido Schimmel wrote:
> On Sun, Mar 18, 2018 at 08:36:01PM -0700, David Ahern wrote:
>> This set is the first of many changes to improve the scalability of the
>> IPv6 code. Follow on changes include:
>> - consolidating duplicate fib6_info references like IPv4 does with
>>   duplicate fib_info
> 
> Before that you need to further break fib6_info into fib6_info and
> fib6_alias, or I misunderstood you?
> 

I was only listing the high level intent - to consolidate duplication. I
have not looked into that step yet, but I suspect that split can be done
in the same patch set as consolidating duplicate fib6_info.

As you know, my preference is to move to nexthop objects (makes fib6_nh
optional). I have IPv4 done; IPv6 requires this patch set. To get there
the patch sequence is:
1. separate data structures for fib and dst paths (this set),

2. cleanup set on top of this one (separate set only because this one is
at 21 patches), and

3. nexthop API.