From: Qais Yousef <qyousef@layalina.io>
To: David Dai <davidai@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Qais Yousef <qyousef@google.com>,
Quentin Perret <qperret@google.com>,
Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1] sched/uclamp: Introduce SCHED_FLAG_RESET_UCLAMP_ON_FORK flag
Date: Fri, 28 Apr 2023 12:57:55 +0100 [thread overview]
Message-ID: <20230428115755.7uklfd4fmpoee4dp@airbuntu> (raw)
In-Reply-To: <20230419175414.ycnlaperdkjxgypx@airbuntu>
On 04/19/23 18:54, Qais Yousef wrote:
[...]
> I was considering to have something a bit more generic that allows selecting
> which attributes to reset.
>
> For example a syscall with SCHED_FLAG_RESET_ON_FORK_SEL combined with
> SCHED_FLAG_UCLAMP_MIN/MAX will only reset those. This should make it extensible
> if we have other similar use cases in the future. The downside it *might*
> require to be done in a separate syscall to the one that sets these parameter.
> But it should be done once.
>
> Maybe there's a better interface, but I think it makes sense to do it in a way
> that we won't have to do this again. Would be good to hear from maintainers
> first before you take my word for it ;-)
Actually I think we can do a better and simpler generic interface. We don't
need a new flag. We can just add a new parameter for what to reset on fork.
When this value is 0 (which it should be by default), it means reset
everything.
// pseudo code
#define RESET_ON_FORK_ALL 0
#define RESET_ON_FORK_POLICY BIT(1) // implies resetting priority
#define RESET_ON_FORK_PRIORITY BIT(2)
#define RESET_ON_FORK_UCLAMP BIT(3)
struct sched_attr {
...
__u64 sched_reset_on_fork_flags;
};
Cheers
--
Qais Yousef
next prev parent reply other threads:[~2023-04-28 11:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 21:34 David Dai
2023-04-19 5:18 ` Dietmar Eggemann
2023-04-20 1:11 ` David Dai
2023-04-20 9:37 ` Dietmar Eggemann
2023-04-20 13:44 ` Vincent Guittot
2023-04-20 16:25 ` Saravana Kannan
2023-04-20 17:49 ` Qais Yousef
2023-04-21 15:10 ` Vincent Guittot
2023-04-28 11:44 ` Qais Yousef
2023-04-20 16:22 ` Saravana Kannan
2023-04-20 17:37 ` Qais Yousef
2023-04-19 17:54 ` Qais Yousef
2023-04-19 22:49 ` Saravana Kannan
2023-04-20 13:38 ` Qais Yousef
2023-04-28 11:57 ` Qais Yousef [this message]
2023-04-28 18:12 ` Saravana Kannan
2023-05-03 13:29 ` Qais Yousef
2023-05-03 15:55 ` Saravana Kannan
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=20230428115755.7uklfd4fmpoee4dp@airbuntu \
--to=qyousef@layalina.io \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=davidai@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®