public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <andrea.righi@linux.dev>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Provide a per-scheduler unique sequence counter
Date: Tue, 1 Oct 2024 15:29:02 +0200	[thread overview]
Message-ID: <Zvv5HpBjzo_T5rub@gpd3> (raw)
In-Reply-To: <Zvru7Qx4aZ9MVU6G@slm.duckdns.org>

On Mon, Sep 30, 2024 at 08:33:17AM -1000, Tejun Heo wrote:
> Hello, Andrea.
> 
> On Fri, Sep 27, 2024 at 06:59:01PM +0200, Andrea Righi wrote:
> ...
> > @@ -662,6 +662,13 @@ struct sched_ext_ops {
> >  	 */
> >  	u64 hotplug_seq;
> >  
> > +	/*
> > +	 * enable_seq - unique per-scheduler counter that can be accessed from
> > +	 * user-space to determine if a scheduler (within a specific hierarchy)
> > +	 * has been restarted.
> > +	 */
> > +	s64 enable_seq;
> 
> Let's just make it a global variable for now. When we package up context for
> each scheduler instance into a struct, it will get packaged up together.
> It's a bit odd to add enable_seq to ops as userspace can't do anything with
> it (note that hotplug_seq is different in that it's provided by the
> userspace on load).

Yep, makes sense, I just sent it because it was mentioned in the other
thread about enable_seq, but we don't really need it right now, so we
can just ignore it for now.

Thanks,
-Andrea

      reply	other threads:[~2024-10-01 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 16:59 [PATCH] sched_ext: Provide a per-scheduler unique sequence counter Andrea Righi
2024-09-30 18:33 ` Tejun Heo
2024-10-01 13:29   ` Andrea Righi [this message]

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=Zvv5HpBjzo_T5rub@gpd3 \
    --to=andrea.righi@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --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