Re: lots of network interfaces
i am asking for ca 800 tun(4) interfaces active but no more than 250Mbit/s over them total. Do you hit CPU limits at that point? i am not because i don't do this now, and ask BEFORE planning. Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: lots of network interfaces
Hello, Wojciech. You wrote 8 марта 2013 г., 20:14:59: WP i am not because i don't do this now, and ask BEFORE planning. I know ISP, who uses FreeBSD with mpd5 as BRAS for PPPoE. They uses ngX, not tunX, but as far as I understand, their systems has thousands such interfaces (~2500 per machine, like 4xCore Supermicro platform, nothing like Really Big Iron). -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: lots of network interfaces
You wrote 8 ? 2013 ?., 20:14:59: WP i am not because i don't do this now, and ask BEFORE planning. I know ISP, who uses FreeBSD with mpd5 as BRAS for PPPoE. They uses exactly what i want, just with vtun. So it will go fine. thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: lots of network interfaces
dte...@freebsd.org writes: I decided to stress-test the netgraph(4) subsystem one day and was able to create 65530 interfaces before it produced an error, refusing to create another. At that point, the system was still usable, but... It took over an hour for ifconfig to list all the interfaces. Simply typing ifconfig with no arguments and pressing ENTER would start spewing information on-screen for over an hour before it finished. (so I'd say that there could be some optimizations made; but nonetheless impressive that the system was still very usable at that point, ifconfig aside). The interfaces are a linked list, plus there's a separate kernel dive for each interface. The list (as opposed to individual interfaces) is really only accessed from userland, so optimizing these operations would need a really good use case to be worthwhile. The current implementation is not just very well known, it's good for hundreds to thousands of interfaces..For the output of ifconfig alone, it might be possible to grab more information in the original getifaddrs() (which makes a copy of the interface list), but that would make other operations with that function more expensive. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: lots of network interfaces
very usable at that point, ifconfig aside). The interfaces are a linked list, plus there's a separate kernel dive for each interface. The list (as opposed to individual interfaces) is i don't care how fast ifconfig displays them, just for how fast things like routing or ipfw rule like via tun196 would work. if it is hashed somehow - fine. if not - very bad. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
