From: Andrea Righi <andrea.righi@linux.dev>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Documentation: Fix typo in sched-ext.rst
Date: Wed, 20 Nov 2024 10:36:24 +0100 [thread overview]
Message-ID: <Zz2tmE2d9k5CqbS1@gpd3> (raw)
In-Reply-To: <20241118024818.11590-1-zhujun2@cmss.chinamobile.com>
Hi Zhu,
On Sun, Nov 17, 2024 at 06:48:18PM -0800, Zhu Jun wrote:
> The word 'tranfers' is wrong, so fix it.
>
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
> ---
> Documentation/scheduler/sched-ext.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-ext.rst b/Documentation/scheduler/sched-ext.rst
> index 7b59bbd2e564..aff1304d2637 100644
> --- a/Documentation/scheduler/sched-ext.rst
> +++ b/Documentation/scheduler/sched-ext.rst
> @@ -265,7 +265,7 @@ The following briefly shows how a waking task is scheduled and executed.
> rather than performing them immediately. There can be up to
> ``ops.dispatch_max_batch`` pending tasks.
>
> - * ``scx_bpf_consume()`` tranfers a task from the specified non-local DSQ
> + * ``scx_bpf_consume()`` transfer a task from the specified non-local DSQ
Actually it should be "transfers".
However, this will be fixed by 5209c03c8ed2 ("sched_ext: Rename
scx_bpf_consume() to scx_bpf_dsq_move_to_local()") that just renames
"transfers" into "moves".
> to the dispatching DSQ. This function cannot be called with any BPF
> locks held. ``scx_bpf_consume()`` flushes the pending dispatched tasks
> before trying to consume the specified DSQ.
> --
> 2.17.1
>
>
>
Thanks,
-Andrea
prev parent reply other threads:[~2024-11-20 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 2:48 [PATCH] sched_ext: Documentation: Fix typo in sched-ext.rst Zhu Jun
2024-11-20 9:36 ` 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=Zz2tmE2d9k5CqbS1@gpd3 \
--to=andrea.righi@linux.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhujun2@cmss.chinamobile.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