From: Phil Auld <pauld@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: andrea.righi@linux.dev, David Vernet <void@manifault.com>,
Giovanni Gherdovich <giovanni.gherdovich@suse.com>,
Kleber Sacilotto de Souza <kleber.souza@canonical.com>,
Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Provide a sysfs enable_seq counter
Date: Mon, 23 Sep 2024 12:45:48 +0200 [thread overview]
Message-ID: <20240923104548.GA308802@pauld.westford.csb> (raw)
In-Reply-To: <ZvCKPkwwC9-o2dsQ@mtj.duckdns.org>
Hi Tejun,
On Sun, Sep 22, 2024 at 11:21:02AM -1000 Tejun Heo wrote:
> Hello, Andrea.
>
> On Sat, Sep 21, 2024 at 09:39:21PM +0200, andrea.righi@linux.dev wrote:
> > static struct attribute *scx_global_attrs[] = {
> > &scx_attr_state.attr,
> > &scx_attr_switch_all.attr,
> > &scx_attr_nr_rejected.attr,
> > &scx_attr_hotplug_seq.attr,
> > + &scx_attr_enable_seq.attr,
> > NULL,
> > };
>
> Can you put this in scx_sched_attrs instead as it probably would make sense
> to track this per-scheduler in the future when we support stacked
> schedulers.
It's not a per scheduler counter, though. It's global. We want to know
that a (any) scx scheduler has been loaded at some time in the past. It's
really only interesting when 0 or > 0. The actual non-zero number and which
scheduler(s) don't matter that much.
And it needs to persist when the scheduler is unloaded (I didn't look but
I uspect the per scheduler attrs come and go?).
Cheers,
Phil
>
> Thanks.
>
> --
> tejun
>
--
next prev parent reply other threads:[~2024-09-23 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 19:39 [PATCH] sched_ext: Provide a sysfs enable_seq counter andrea.righi
2024-09-22 21:21 ` Tejun Heo
2024-09-23 10:45 ` Phil Auld [this message]
2024-09-23 15:14 ` Andrea Righi
2024-09-23 15:32 ` Tejun Heo
2024-09-23 16:00 ` Phil Auld
2024-09-23 16:34 ` Andrea Righi
2024-09-23 16:47 ` Tejun Heo
2024-09-23 16:57 ` Phil Auld
2024-09-23 17:01 ` Tejun Heo
2024-09-23 17:16 ` andrea.righi
2024-09-23 10:48 ` Phil Auld
2024-09-23 16:53 ` Tejun Heo
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=20240923104548.GA308802@pauld.westford.csb \
--to=pauld@redhat.com \
--cc=andrea.righi@linux.dev \
--cc=giovanni.gherdovich@suse.com \
--cc=kleber.souza@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=tj@kernel.org \
--cc=void@manifault.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