[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160718151841.GA19066@breakpoint.cc>
Date: Mon, 18 Jul 2016 17:18:41 +0200
From: Florian Westphal <fw@...len.de>
To: kan.liang@...el.com
Cc: davem@...emloft.net, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
jeffrey.t.kirsher@...el.com, mingo@...hat.com,
peterz@...radead.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net,
akpm@...ux-foundation.org, keescook@...omium.org,
viro@...iv.linux.org.uk, gorcunov@...nvz.org,
john.stultz@...aro.org, aduyck@...antis.com, ben@...adent.org.uk,
decot@...glers.com, jesse.brandeburg@...el.com, andi@...stfloor.org
Subject: Re: [RFC PATCH 00/30] Kernel NET policy
kan.liang@...el.com <kan.liang@...el.com> wrote:
> From: Kan Liang <kan.liang@...el.com>
>
> It is a big challenge to get good network performance. First, the network
> performance is not good with default system settings. Second, it is too
> difficult to do automatic tuning for all possible workloads, since workloads
> have different requirements. Some workloads may want high throughput.
Seems you did lots of tests to find optimal settings for a given base
policy.
What is missing in the kernel UAPI so userspace could do these settings
on its own, without adding this policy stuff to the kernel?
It seems strange to me to add such policies to the kernel.
Addmittingly, documentation of some settings is non-existent and one needs
various different tools to set this (sysctl, procfs, sysfs, ethtool, etc).
But all of these details could be hidden from user.
Have you looked at tuna for instance?
Powered by blists - more mailing lists