netdev - Re: [PATCH net-next] rtnetlink: Support fine-grained netdevice bulk deletion

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: <20211124094443.409ab643@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Wed, 24 Nov 2021 09:44:43 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Gilad Naaman <gnaaman@...venets.com>
Cc:     dsahern@...il.com, lschlesinger@...venets.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next] rtnetlink: Support fine-grained netdevice bulk
 deletion

On Wed, 24 Nov 2021 18:59:42 +0200 Gilad Naaman wrote:
> > I'm sorry I don't understand. Please provide a clear use case.
> > I've never heard of "factory default on a large server".  
> 
> Our company is developing a core-router that is supposed to support thousands
> of links, both physical and virtual. (e.g. loopbacks, tunnels, vrfs, etc)
> 
> At times we are required to configure massive amounts of interfaces at once,
> such as when a factory reset is performed on the router (causing a deletion
> of all links), a configuration is restored after an upgrade,
> or really whenever the system reboots.
> 
> The significant detail in Lahav's benchmark is not "deleting 10K loopbacks",
> it's "deleting 10K interfaces", which *is* a good representation of what we're
> trying to do.

Alright, no fundamental objections here if you do in fact need this.
Please address the review comments.