From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
sergio.collado@gmail.com, peterz@infradead.org,
rdunlap@infradead.org
Cc: bilbao@vt.edu, jembid@ucm.es, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/1] docs: scheduler: Start documenting the EEVDF scheduler
Date: Fri, 19 Jul 2024 19:07:08 -0500 [thread overview]
Message-ID: <55674f3f-30d5-4da4-8fe2-0efafec5d3bb@gmail.com> (raw)
In-Reply-To: <878qy1uvyw.fsf@trenco.lwn.net>
On 7/16/24 11:45, Jonathan Corbet wrote:
> Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:
>
>> Add some documentation regarding the newly introduced scheduler EEVDF.
> A nit, but one I wish more people would make note of...
>
> [...]
>
>> --- a/Documentation/scheduler/sched-design-CFS.rst
>> +++ b/Documentation/scheduler/sched-design-CFS.rst
>> @@ -8,10 +8,12 @@ CFS Scheduler
>> 1. OVERVIEW
>> ============
>>
>> -CFS stands for "Completely Fair Scheduler," and is the new "desktop" process
>> -scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. It is the
>> -replacement for the previous vanilla scheduler's SCHED_OTHER interactivity
>> -code.
>> +CFS stands for "Completely Fair Scheduler," and is the "desktop" process
>> +scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. When
>> +originally merged, it was the replacement for the previous vanilla
>> +scheduler's SCHED_OTHER interactivity code. Nowadays, CFS is making room
>> +for EEVDF, for which documentation can be found in
>> +:ref:`sched_design_EEVDF`.
> If, here, you just say "can be found in
> Documentation/scheduler/sched-eevdf.rst", the right cross-reference will
> be created and ...
>
>> 80% of CFS's design can be summed up in a single sentence: CFS basically models
>> an "ideal, precise multi-tasking CPU" on real hardware.
>> diff --git a/Documentation/scheduler/sched-eevdf.rst b/Documentation/scheduler/sched-eevdf.rst
>> new file mode 100644
>> index 000000000000..019327da333a
>> --- /dev/null
>> +++ b/Documentation/scheduler/sched-eevdf.rst
>> @@ -0,0 +1,44 @@
>> +.. _sched_design_EEVDF:
> ...you can take out this unnecessary label.
Love it! Labels are a source of warnings.
Sending v3 now.
>
> Thanks,
>
> jon
Thanks,
Carlos
prev parent reply other threads:[~2024-07-20 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 14:04 [PATCH v2 0/1] docs: scheduler: Start documenting the EEVDF scheduler Carlos Bilbao
2024-07-13 14:04 ` [PATCH v2 1/1] " Carlos Bilbao
2024-07-14 13:40 ` Sergio González Collado
2024-07-15 5:15 ` Naik, Avadhut
2024-07-16 16:45 ` Jonathan Corbet
2024-07-20 0:07 ` Carlos Bilbao [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=55674f3f-30d5-4da4-8fe2-0efafec5d3bb@gmail.com \
--to=carlos.bilbao.osdev@gmail.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=jembid@ucm.es \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sergio.collado@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