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
| ||
|
Message-ID: <5b949924-65bb-9b6d-0e7f-252c12476849@kernel.org> Date: Thu, 18 May 2023 20:35:02 -0600 From: David Ahern <dsahern@...nel.org> To: Kui-Feng Lee <sinquersw@...il.com>, Kui-Feng Lee <thinker.li@...il.com>, netdev@...r.kernel.org, ast@...nel.org, martin.lau@...ux.dev, kernel-team@...a.com, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com Cc: Kui-Feng Lee <kuifeng@...a.com>, Ido Schimmel <idosch@...sch.org> Subject: Re: [RFC PATCH net-next v2 0/2] Mitigate the Issue of Expired Routes in Linux IPv6 Routing Tables On 5/18/23 12:51 PM, Kui-Feng Lee wrote: > This is one of solutions I considered at beginning. > With this approach, we can have a maximum > number of entries like what neighbor tables do. > Remove entries only if the list reach the maximum without running > a GC timer. However, it can be very inefficient to insert a new entry > ordered. Stephen mentioned 3 million routes on backbone router > in another message. We may need something more complicated > like RB-tree or HEAP to reduce the overhead. I do not believe so. Not every route will have an expiration timer. Only those are added to the new, time ordered list_head. And you can not cap the number of entries in a FIB.
Powered by blists - more mailing lists