linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: tj@kernel.org, hannes@cmpxchg.org, lizefan.x@bytedance.com,
	peterz@infradead.org, johunt@akamai.com, keescook@chromium.org,
	quic_sudaraja@quicinc.com, cgroups@vger.kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] psi: remove 500ms min window size limitation for triggers
Date: Thu, 2 Mar 2023 14:58:25 +0100	[thread overview]
Message-ID: <ZACrgV4f39P/2sZO@dhcp22.suse.cz> (raw)
In-Reply-To: <20230301193403.1507484-1-surenb@google.com>

On Wed 01-03-23 11:34:03, Suren Baghdasaryan wrote:
> Current 500ms min window size for psi triggers limits polling interval
> to 50ms to prevent polling threads from using too much cpu bandwidth by
> polling too frequently. However the number of cgroups with triggers is
> unlimited, so this protection can be defeated by creating multiple
> cgroups with psi triggers (triggers in each cgroup are served by a single
> "psimon" kernel thread).
> Instead of limiting min polling period, which also limits the latency of
> psi events, it's better to limit psi trigger creation to authorized users
> only, like we do for system-wide psi triggers (/proc/pressure/* files can
> be written only by processes with CAP_SYS_RESOURCE capability). This also
> makes access rules for cgroup psi files consistent with system-wide ones.
> Add a CAP_SYS_RESOURCE capability check for cgroup psi file writers and
> remove the psi window min size limitation.
> 
> Suggested-by: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>
> Link: https://lore.kernel.org/all/cover.1676067791.git.quic_sudaraja@quicinc.com/
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>

Acked-by: Michal Hocko <mhocko@suse.com>

with this to fix
[...]
> @@ -1278,8 +1277,7 @@ struct psi_trigger *psi_trigger_create(struct psi_group *group,
>  	if (state >= PSI_NONIDLE)
>  		return ERR_PTR(-EINVAL);
>  
> -	if (window_us < WINDOW_MIN_US ||
> -		window_us > WINDOW_MAX_US)
> +	if (window_us <= 0 || window_us > WINDOW_MAX_US)
>  		return ERR_PTR(-EINVAL);

window_us is u32 sp the check for <= 0 doesn't make any sense.

>  
>  	/* Check threshold */
> -- 
> 2.40.0.rc0.216.gc4246ad0f0-goog

-- 
Michal Hocko
SUSE Labs


  parent reply	other threads:[~2023-03-02 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 19:34 [PATCH 1/1] psi: remove 500ms min window size limitation for triggers Suren Baghdasaryan
2023-03-01 20:07 ` Johannes Weiner
2023-03-01 20:48   ` Suren Baghdasaryan
2023-03-01 21:00     ` Kalesh Singh
2023-03-02 15:30     ` Johannes Weiner
2023-03-02 16:13       ` Suren Baghdasaryan
2023-03-02 17:41         ` Michal Hocko
2023-03-02 17:58           ` Johannes Weiner
2023-03-02 13:58 ` Michal Hocko [this message]
2023-03-02 16:08   ` Suren Baghdasaryan
2023-03-02 17:39     ` Michal Hocko

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=ZACrgV4f39P/2sZO@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=johunt@akamai.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan.x@bytedance.com \
    --cc=peterz@infradead.org \
    --cc=quic_sudaraja@quicinc.com \
    --cc=surenb@google.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).