From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.or, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: update scx_bpf_dsq_insert() doc for SCX_DSQ_LOCAL_ON
Date: Mon, 6 Jan 2025 08:56:15 -1000 [thread overview]
Message-ID: <Z3wnT5xPn2LuQFow@slm.duckdns.org> (raw)
In-Reply-To: <20250106170309.205385-1-arighi@nvidia.com>
On Mon, Jan 06, 2025 at 06:03:09PM +0100, Andrea Righi wrote:
> With commit 5b26f7b920f7 ("sched_ext: Allow SCX_DSQ_LOCAL_ON for direct
> dispatches"), scx_bpf_dsq_insert() can use SCX_DSQ_LOCAL_ON for direct
> dispatch from ops.enqueue() to target the local DSQ of any CPU.
>
> Update the documentation accordingly.
>
> Fixes: 5b26f7b920f7 ("sched_ext: Allow SCX_DSQ_LOCAL_ON for direct dispatches")
> Signed-off-by: Andrea Righi <arighi@nvidia.com>
Applied to sched_ext/for-6.14.
Thanks.
--
tejun
prev parent reply other threads:[~2025-01-06 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 17:03 [PATCH] sched_ext: update scx_bpf_dsq_insert() doc for SCX_DSQ_LOCAL_ON Andrea Righi
2025-01-06 18:56 ` Tejun Heo [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=Z3wnT5xPn2LuQFow@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.or \
--cc=linux-kernel@vger.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