From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Dawei Li <daweilics@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: when/how is the schedule() function actually called?
Date: Fri, 08 Dec 2023 12:44:56 -0500 [thread overview]
Message-ID: <115587.1702057496@turing-police> (raw)
In-Reply-To: <CAG5MgCpmkwwSTdWTa8AYnktuAeMzGcYtZMkZNx151K30eOxiUA@mail.gmail.com>
On Sat, 09 Dec 2023 00:16:32 +0800, Dawei Li said:
> Greetings!
> (Although I am using the 2.6.34 version, I believe the question is generally
> applicable to any kernel version.)
That is, in general, a bad assumption when you are looking at kernel versions
old enough that they count as digital archaeology....
[/usr/src/linux-next] git show v2.6.34
tag v2.6.34
Tagger: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun May 16 14:17:44 2010 -0700
[/usr/src/linux-next] git diff --shortstat v2.6.34..next-20231205
96965 files changed, 32056985 insertions(+), 7606202 deletions(-)
Given that next-20231205 has just over 33 million lines of code, we're well
into territory where there's a vanishing small percentage of code still
remaining unchanged from 2010.
And yes, that means that even basic functions schedule() and friends have been
reworked in he past decade and a half....
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-12-08 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 16:16 when/how is the schedule() function actually called? Dawei Li
2023-12-08 17:44 ` Valdis Klētnieks [this message]
2023-12-08 18:21 ` Dawei Li
2023-12-08 19:10 ` Billie Alsup (balsup)
2023-12-10 16:59 ` Dawei Li
2023-12-14 17:13 ` Billie Alsup (balsup)
2023-12-08 19:47 ` iso m
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 5:59 Dawei Li
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=115587.1702057496@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=daweilics@gmail.com \
--cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.