Date: Sun, 29 Oct 2023 00:05:10 +0700 From: Eugene Grosbein <eugen@freebsd.org> To: Roy Marples <roy@marples.name> Cc: freebsd-net@freebsd.org Subject: =?UTF-8?Q?Re:_=c2=a0netif_userland_API?= Message-ID: <888002a5-4bb1-df09-b2c0-7ef95e8d5ed1@freebsd.org> In-Reply-To: <18b772ae647.bd4beee8172897.5493704673952375764@marples.name> References: <f889550b-191d-efdd-4346-7b5b060ee53a@freebsd.org> <18b77179746.d0c6d171174837.5548971766419580308@marples.name> <847fa0cf-db1e-45b3-3a0a-37dd647dabc9@freebsd.org> <18b772ae647.bd4beee8172897.5493704673952375764@marples.name>
next in thread | previous in thread | raw e-mail | index | archive | help
28.10.2023 23:43, Roy Marples wrote: > Using netlink rather than route on a modern FreeBSD kernel may allow you do do the same thing > but install a kernel filter on the socket just to receive interface changes. > > That should match your requirements. This scales bad still. More new vlans under single parent we have, more system calls to list them, longer wall clock time util listing completition and more burden for the system as a whole. I'm talking about *efficient* API. Eugene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?888002a5-4bb1-df09-b2c0-7ef95e8d5ed1>