lvs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Wiesner <jwiesner@suse.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
	lvs-devel@vger.kernel.org,
	yunhong-cgl jiang <xintian1976@gmail.com>,
	yunhjiang@ebay.com, dust.li@linux.alibaba.com,
	tangyang@zhihu.com
Subject: Re: [RFC PATCH 3/4] ipvs: add est_cpulist and est_nice sysctl vars
Date: Mon, 5 Sep 2022 16:53:33 +0200	[thread overview]
Message-ID: <20220905145333.GE18621@incl> (raw)
In-Reply-To: <20220827174154.220651-4-ja@ssi.bg>

On Sat, Aug 27, 2022 at 08:41:53PM +0300, Julian Anastasov wrote:
> Allow the kthreads for stats to be configured for
> specific cpulist (isolation) and niceness (scheduling
> priority).
> 
> Signed-off-by: Julian Anastasov <ja@ssi.bg>

I think moving the estimation kthreads to idle CPU core will become necessary for people who want their estimates to be as accurate as possible. Otherwise, scheduling latencies on busy systems may make the estimates inaccurate by delaying the kthreads after they have been woken up.

Reviewed-by: Jiri Wiesner <jwiesner@suse.de>

> diff --git a/Documentation/networking/ipvs-sysctl.rst b/Documentation/networking/ipvs-sysctl.rst
> index 387fda80f05f..90c7c325421a 100644
> --- a/Documentation/networking/ipvs-sysctl.rst
> +++ b/Documentation/networking/ipvs-sysctl.rst
> @@ -129,6 +129,26 @@ drop_packet - INTEGER
>  	threshold. When the mode 3 is set, the always mode drop rate
>  	is controlled by the /proc/sys/net/ipv4/vs/am_droprate.
>  
> +est_cpulist - CPULIST
> +	Allowed	CPUs for estimation kthreads
> +
> +	Syntax: standard cpulist format
> +	empty list - stop kthread tasks and estimation
> +	default - the system's housekeeping CPUs for kthreads
> +
> +	Example:
> +	"all": all possible CPUs
> +	"0-N": all possible CPUs, N denotes last CPU number
> +	"0,1-N:1/2": first and all CPUs with odd number
> +	"": empty list
> +
> +est_nice - INTEGER
> +	default 0
> +	Valid range: -20 (more favorable) - 19 (less favorable)

How about using dots instead of a hyphen in the range? I guess it will be easier to read.

> +
> +	Niceness value to use for the estimation kthreads (scheduling
> +	priority)
> +
>  expire_nodest_conn - BOOLEAN
>  	- 0 - disabled (default)
>  	- not 0 - enabled

-- 
Jiri Wiesner
SUSE Labs

  reply	other threads:[~2022-09-05 14:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27 17:41 [RFC PATCH 0/4] Use kthreads for stats Julian Anastasov
2022-08-27 17:41 ` [RFC PATCH 1/4] ipvs: add rcu protection to stats Julian Anastasov
2022-09-05 10:43   ` Jiri Wiesner
2022-08-27 17:41 ` [RFC PATCH 2/4] ipvs: use kthreads for stats estimation Julian Anastasov
2022-09-05  6:47   ` dust.li
2022-09-07 18:07     ` Julian Anastasov
2022-09-05 13:19   ` Jiri Wiesner
2022-09-07 19:01     ` Julian Anastasov
2022-09-08 16:00       ` Jiri Wiesner
2022-08-27 17:41 ` [RFC PATCH 3/4] ipvs: add est_cpulist and est_nice sysctl vars Julian Anastasov
2022-09-05 14:53   ` Jiri Wiesner [this message]
2022-08-27 17:41 ` [RFC PATCH 4/4] ipvs: run_estimation should control the kthread tasks Julian Anastasov
2022-09-05 14:57   ` Jiri Wiesner
2022-09-05  6:34 ` [RFC PATCH 0/4] Use kthreads for stats dust.li
2022-09-05  8:26 ` Jiri Wiesner
2022-09-07 18:33   ` Julian Anastasov
2022-09-08 15:35     ` Jiri Wiesner
2022-09-08 18:32       ` Jiri Wiesner

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=20220905145333.GE18621@incl \
    --to=jwiesner@suse.de \
    --cc=dust.li@linux.alibaba.com \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=tangyang@zhihu.com \
    --cc=xintian1976@gmail.com \
    --cc=yunhjiang@ebay.com \
    /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).