From: Anton Danilov <littlesmilingcloud@gmail.com>
To: netdev@vger.kernel.org
Subject: Linux router kernel configuration
Date: Tue, 23 Aug 2016 23:28:19 +0300 [thread overview]
Message-ID: <E1bcIJ1-0004T6-Do@danilov> (raw)
Hello everyone.
I'm working in a small ISP company, and we're using x86 servers under debian as core and border routers.
The pair of core routers (active-backup redundancy scheme) are the dual-socket servers with Xeon E5-2637 v2 CPUs and one 82599EB dual-port 10G NIC. Tasks of these routers: traffic shaping (HTB+pfifo with u32 hashing classifier), content filtering (ipset + nfqueue + suricata) and some blocking of access with ipset address sets. Average duplex traffic is couple of gigabits per second / several hundreds of kpps. Currently we're using the custom configurated 3.10 kernel on these servers.
I have several questions about kernel configuration in which I'm stuck or doubt:
1. Kernel version. What is the kernel better for these tasks at now? I'm think about usage of latest LTS kernel (4.4).
1. Timers subsystem: periodic ticks / idle dynticks / full dynticks. Are there some recomendations? Currently I'm using periodic ticks with 1000HZ frequency. Maybe is there better choice?
2. Preemption model. I'm using the no forced preemption on routers.
3. Power management. Should I disable the processor power management features in kernel config or use the kernel cmd line boot options like processor.max_cstate = 0 and intel_idle.max_cstate = 0?
4. Hyper-threading usage. I've disabled it in the bios to avoid a unefficient cache usage. But maybe someone have opposite view on this feature.
Thanks for your attention and advices.
---
With best regards
Anton Danilov mailto://littlesmilingcloud@gmail.com
reply other threads:[~2016-08-23 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1bcIJ1-0004T6-Do@danilov \
--to=littlesmilingcloud@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox