public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <arighi@nvidia.com>
To: Changwoo Min <multics69@gmail.com>
Cc: tj@kernel.org, void@manifault.com, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, sched-ext@meta.com, me@mostlynerdless.de,
	ggherdovich@suse.com, dschatzberg@meta.com, yougmark94@gmail.com,
	changwoo@igalia.com, kernel-dev@igalia.com
Subject: Re: [PATCH 2/3] sched_ext: Rename scx_bpf_consume() to scx_bpf_dsq_move_to_local()
Date: Sun, 10 Nov 2024 12:52:47 +0100	[thread overview]
Message-ID: <ZzCej_1NNr2wB0AD@gpd3> (raw)
In-Reply-To: <81281555-d57f-4507-a3a5-ea9d1aa27871@gmail.com>

On Sun, Nov 10, 2024 at 07:03:03PM +0900, Changwoo Min wrote:
> Hello Tejun,
> 
> Overall looks good to me. I have one minior comment:
> 
> On 24. 11. 10. 04:48, Tejun Heo wrote:
> > @@ -6372,9 +6372,8 @@ __bpf_kfunc void scx_bpf_dispatch(struct task_struct *p, u64 dsq_id, u64 slice,
> >    * @enq_flags: SCX_ENQ_*
> >    *
> >    * Insert @p into the vtime priority queue of the DSQ identified by @dsq_id.
> > - * Tasks queued into the priority queue are ordered by @vtime and always
> > - * consumed after the tasks in the FIFO queue. All other aspects are identical
> > - * to scx_bpf_dsq_insert().
> > + * Tasks queued into the priority queue are ordered by @vtime. All other aspects
> > + * are identical to scx_bpf_dsq_insert().
> 
> I suggest keeping this part, "and always consumed after the tasks
> in the FIFO queue." Otherwise, IIRC, there is no place to explain
> the priority between FIFO and priority DSQs explicitly.

I think we don't allow anymore to use the FIFO queue and the prio queue
at the same time. Maybe we should clarify this here and also mention
that we can't use scx_bpf_dsq_insert_vtime() with the built-in DSQs.

Thanks,
-Andrea

  reply	other threads:[~2024-11-10 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09 19:48 [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs Tejun Heo
2024-11-09 19:48 ` [PATCH 1/3] sched_ext: Rename scx_bpf_dispatch[_vtime]() to scx_bpf_dsq_insert[_vtime]() Tejun Heo
2024-11-09 19:48 ` [PATCH 2/3] sched_ext: Rename scx_bpf_consume() to scx_bpf_dsq_move_to_local() Tejun Heo
2024-11-10 10:03   ` Changwoo Min
2024-11-10 11:52     ` Andrea Righi [this message]
2024-11-10 16:09       ` Johannes Bechberger
2024-11-10 19:38         ` Tejun Heo
2024-11-09 19:48 ` [PATCH 3/3] sched_ext: Rename scx_bpf_dispatch[_vtime]_from_dsq*() -> scx_bpf_dsq_move[_vtime]*() Tejun Heo
2024-11-10 11:45 ` [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs Andrea Righi
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10 20:02 Tejun Heo
2024-11-10 20:02 ` [PATCH 2/3] sched_ext: Rename scx_bpf_consume() to scx_bpf_dsq_move_to_local() 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=ZzCej_1NNr2wB0AD@gpd3 \
    --to=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=dschatzberg@meta.com \
    --cc=ggherdovich@suse.com \
    --cc=kernel-dev@igalia.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@mostlynerdless.de \
    --cc=multics69@gmail.com \
    --cc=sched-ext@meta.com \
    --cc=tj@kernel.org \
    --cc=void@manifault.com \
    --cc=yougmark94@gmail.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