From: Stephen Hemminger <stephen@networkplumber.org>
To: kan.liang@intel.com
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
mingo@redhat.com, peterz@infradead.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
akpm@linux-foundation.org, keescook@chromium.org,
viro@zeniv.linux.org.uk, gorcunov@openvz.org,
john.stultz@linaro.org, aduyck@mirantis.com, ben@decadent.org.uk,
decot@googlers.com, fw@strlen.de, alexander.duyck@gmail.com,
daniel@iogearbox.net, tom@herbertland.com, rdunlap@infradead.org,
xiyou.wangcong@gmail.com, hannes@stressinduktion.org,
jesse.brandeburg@intel.com, andi@firstfloor.org
Subject: Re: [RFC V2 PATCH 00/25] Kernel NET policy
Date: Thu, 4 Aug 2016 17:03:32 -0700 [thread overview]
Message-ID: <20160804170332.4304a907@xeon-e3> (raw)
In-Reply-To: <1420076354-4861-1-git-send-email-kan.liang@intel.com>
On Wed, 31 Dec 2014 20:38:49 -0500
kan.liang@intel.com wrote:
> 5. Why disable IRQ balance?
> A: Disabling IRQ balance is a common way (recommend way for some devices) to
> tune network performance.
I appreciate that network tuning is hard, most people get it wrong, and nobody
agrees on the right answer.
So rather than fixing existing tools or writing new userspace tools to do network
tuning, you want to hard code one policy manager in kernel with a /proc interface.
Why not make a good userspace tool (like powertop). There are also several IRQ
balancing programs, but since irqbalance was championed by one vendor others seem
to follow like sheep.
I agree that this a real concern but the implementation of this leaves much
to be desired and discussed. Why can't this be done outside of the kernel.
next prev parent reply other threads:[~2016-08-05 0:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 1:38 [RFC V2 PATCH 00/25] Kernel NET policy kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 01/25] net: introduce " kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 02/25] net/netpolicy: init " kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 03/25] net/netpolicy: get device queue irq information kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 04/25] net/netpolicy: get CPU information kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 05/25] net/netpolicy: create CPU and queue mapping kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 06/25] net/netpolicy: set and remove IRQ affinity kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 07/25] net/netpolicy: enable and disable NET policy kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 08/25] net/netpolicy: introduce NET policy object kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 09/25] net/netpolicy: set NET policy by policy name kan.liang
2015-01-01 1:38 ` [RFC V2 PATCH 10/25] net/netpolicy: add three new NET policies kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 11/25] net/netpolicy: add MIX policy kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 12/25] net/netpolicy: NET device hotplug kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 13/25] net/netpolicy: support CPU hotplug kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 14/25] net/netpolicy: handle channel changes kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 15/25] net/netpolicy: implement netpolicy register kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 16/25] net/netpolicy: introduce per socket netpolicy kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 17/25] net/netpolicy: introduce netpolicy_pick_queue kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 18/25] net/netpolicy: set Tx queues according to policy kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 19/25] net/netpolicy: set Rx " kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 20/25] net/netpolicy: introduce per task net policy kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 21/25] net/netpolicy: set per task policy by proc kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 22/25] net/netpolicy: fast path for finding the queues kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 23/25] net/netpolicy: optimize for queue pair kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 24/25] net/netpolicy: limit the total record number kan.liang
2015-01-01 1:39 ` [RFC V2 PATCH 25/25] Documentation/networking: Document NET policy kan.liang
2016-08-05 0:03 ` Stephen Hemminger [this message]
2016-08-05 13:44 ` [RFC V2 PATCH 00/25] Kernel " Liang, Kan
2016-08-05 1:31 ` Alexei Starovoitov
-- strict thread matches above, loose matches on Subject: below --
2016-08-04 19:36 kan.liang
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=20160804170332.4304a907@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=aduyck@mirantis.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=andi@firstfloor.org \
--cc=ben@decadent.org.uk \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=decot@googlers.com \
--cc=fw@strlen.de \
--cc=gorcunov@openvz.org \
--cc=hannes@stressinduktion.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jmorris@namei.org \
--cc=john.stultz@linaro.org \
--cc=kaber@trash.net \
--cc=kan.liang@intel.com \
--cc=keescook@chromium.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tom@herbertland.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).