mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Quchaosheng <quchaosheng000406@163.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sched/doc: add a preemption model overview
Date: Wed, 23 Sep 2026 09:28:25 +0200	[thread overview]
Message-ID: <20260923072825._dV0YtYP@linutronix.de> (raw)
In-Reply-To: <20260922083101.99685-1-quchaosheng000406@163.com>

On 2026-09-22 16:31:00 [+0800], Quchaosheng wrote:
> The scheduler documentation describes the individual scheduling classes
> and various tuning knobs, but there is nothing that describes the
> preemption models themselves.  The only place where they are documented
> is the kernel-parameters entry for "preempt=", which explains the boot
> time parameter but not the models it selects.
> Assisted-by: LLM
> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Quchaosheng <quchaosheng000406@163.com>

This reads very nice.
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

Once comment bellow.

…
> --- /dev/null
> +++ b/Documentation/scheduler/sched-preemption.rst
> @@ -0,0 +1,84 @@
> +separates the models:
> +
> +``none``
> +	Code paths with long loops contain explicit ``cond_resched()`` calls,
> +	which perform the scheduling.
> +
> +``voluntary``
> +	As ``none``, and functions which are known to be able to block gain
> +	such a call as well.

I know what you are trying to say but it does not sound obvious that you
refer here to cond_resched(). At least to me.

> +
> +``full``
> +	Explicit preemption points are no longer involved.  The kernel tracks
> +	whether it may be preempted and schedules once the request can be
> +	honoured.
…

Sebastian

      parent reply	other threads:[~2026-09-23  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  8:31 Quchaosheng
2026-09-22  8:31 ` [PATCH v2 2/2] docs: kernel-parameters: fix a truncated sentence for preempt=lazy Quchaosheng
2026-09-23  7:31   ` Sebastian Andrzej Siewior
2026-09-23  7:28 ` Sebastian Andrzej Siewior [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=20260923072825._dV0YtYP@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=quchaosheng000406@163.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    /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

all inboxes | Powered by JetHome®