Date: Tue, 27 Jan 2015 12:15:23 -0800 From: Michael Sierchio <kudzu@tenebras.com> To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@cochard.me> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Jim Thompson <jim@netgate.com>, =?UTF-8?Q?Antoine_Beaupr=C3=A9?= <anarcat@koumbit.org> Subject: Re: is polling still a thing? Message-ID: <CAHu1Y71XDO1fuCJM_Cw1wm4jt%2BigKisaTWRb4gBX3nsaepwMsQ@mail.gmail.com> In-Reply-To: <CA%2Bq%2BTcrkp3U%2Bb5816es3jsvhNfxpW_v%2BRQOa8a9BbLwNTm3RuQ@mail.gmail.com> References: <871tmgceup.fsf@marcos.anarc.at> <A32D80F3-9D34-4136-A870-B28582F6EAA0@netgate.com> <87vbjsaxxy.fsf@marcos.anarc.at> <CA%2Bq%2BTcrkp3U%2Bb5816es3jsvhNfxpW_v%2BRQOa8a9BbLwNTm3RuQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On small, embedded computers running ipfw w/kernel nat and device polling enabled (on em ether adapters), I observed the *reported* system load grow very high. When disabling polling on the interfaces, it went back to something normal. My impression is that the consensus among the core developers concerned with networking is that device polling is an ancient hack and is deprecated. In the case of a DDoS attack, there may be many other things to try - at the infrastructure level - traffic diversion techniques like BGP flowspec, use anycast, etc. On the individual server level, use stateful rules with GRED enabled, dropping most new tcp or udp traffic based on load. That's a topic of its own... - M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y71XDO1fuCJM_Cw1wm4jt%2BigKisaTWRb4gBX3nsaepwMsQ>