Re: net.link.bridge.member_ifaddrs has landed in stable/14

Warner Losh <[email protected]>
Newsgroups gmane.os.freebsd.devel.net
Message-ID <CANCZdfoQ13wNK21jmazE1B4FgxC-Acs6DnKCgvR8hDwqBqv9qQ__23035.6949892425$1747839574$gmane$org@mail.gmail.com>
On Tue, May 20, 2025 at 10:05 PM Lexi Winter <[email protected]> wrote:
>
> hello,
>
> i have just MFC'd the sysctl net.link.bridge.member_addrs to stable/14.
> for detail see: https://cgit.freebsd.org/src/commit/?h=stable/14&id=ff1980d569c8167d38cda5f2713664866d9802bc
>
> in short, if you have a bridge with a lot of members (20+) and you do
> not have any IP addresses assigned to those bridge members, you should
> see a significant performance improvement from enabling this sysctl.
>
> please feel free to test this and report any problems.

So to be clear, this is not the behavior change that's been much
talked about in -current. However, it's related to that change. If
people want to see if they are affected by that, they should set
sysctl net.link.bridge.member_ifaddrs=0 to see if their setup still
works. Of course, you'd want to do that to get the performance benefit
with lots of interfaces, but if you have just a few you might see a
behavior change when you update to -current or stable/15 in the
future. Nothing will break after this change w/o tweaking the sysctl,
but if will behoove you to do some controlled testing in the next year
sometime.

Warner
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.