netdev - Re: [PATCH net-next v2 07/12] rtnetlink: add new rtm tunnel api for tunnel id filtering

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:   Wed, 23 Feb 2022 08:22:55 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Roopa Prabhu <roopa@...dia.com>
Cc:     <davem@...emloft.net>, <netdev@...r.kernel.org>,
        <stephen@...workplumber.org>, <nikolay@...ulusnetworks.com>,
        <idosch@...dia.com>, <dsahern@...il.com>, <bpoirier@...dia.com>
Subject: Re: [PATCH net-next v2 07/12] rtnetlink: add new rtm tunnel api for
 tunnel id filtering

On Tue, 22 Feb 2022 22:31:18 -0800 Roopa Prabhu wrote:
> > Makes sense. I wasn't quite sure if this isn't over-engineering
> >   - do deployments really use VxLAN devs with many VNIs?  
> 
> yes, vnis are unfortunately used to stretch layer 2 domains exceeding 
> the 4k vlan limit
> 
> In the example provided in this series, vnis can be deployed in the 
> ranges of more than 15k if each customer is allocated a 4k vlan range 
> (bridge domain),
> 
> and a single switch can host 3-4 customers.
> 
> the scale is also the reason to switch to dst metadata devices when 
> deployed vni numbers get large. The traditional vxlan netdev per vni 
> does not work well at this scale.

Ah, now it all clicked together, thanks!