kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>
Subject: Re: There is "softlockup_tick()" function in the source code of linux-2.6.32, but what's the corresponding function name in the linux-4.9 or later?
Date: Mon, 6 Jul 2020 10:22:14 +0800	[thread overview]
Message-ID: <CAAvDm6YzfOdgowkJVY8yRUdSX+Ou=V2KtasULm=sGdwbpWmC3w@mail.gmail.com> (raw)
In-Reply-To: <125370.1593975511@turing-police>

Thank you for the clarification.
I have a better understanding of this matter with help.

Valdis Klētnieks <valdis.kletnieks@vt.edu> 于2020年7月6日周一 上午2:58写道:
>
> On Sun, 05 Jul 2020 15:34:32 +0800, "e- d8 i> sunshilong" said:
>
> > There is "softlockup_tick()" function in the source code of
> > linux-2.6.32(refer to
> > https://elixir.bootlin.com/linux/v2.6.32.39/source/kernel/softlockup.c#L104),
> > but what's the corresponding function in the linux-4.9 or later?
> > There is not even a source code file named by softlockup.c in the
> > linux-4.9 or later?
>
> 2.6.32 was a *long* time ago. Heck, even the BKL was still around at that point.
>
> [/usr/src/linux-next] git show v2.6.32
> tag v2.6.32
> Tagger: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Wed Dec 2 19:51:29 2009 -0800
>
> and there were a *lot* of code changes from then until v4.9.
>
> [/usr/src/linux-next] git diff --shortstat v2.6.32..v4.9
>  59438 files changed, 14713566 insertions(+), 4896973 deletions(-)
>
> Even v4.9 is from long ago and far away, and of less and less relevance
> each new Linux release.
>
> [/usr/src/linux-next] git diff --shortstat v4.9..HEAD
>  73256 files changed, 11345968 insertions(+), 4464267 deletions(-)
>
> So.. since 2.6.32. there's been some 26 million new lines of code, which is an
> interestingly high number considering that there's only 27 million lines of
> code in the tree currently.
>
> In other words, essentially *everything* has been completely re-written and
> re-designed since 2.6.32, and "What is the corresponding function" is a
> question that is probably meaningless, because whatever you're looking for from
> back then has almost certainly been completely re-written with a totally new
> approach.
>
> Seriously - 2.6.32 is of interest only to software archaeologists. There is
> nothing worth looking at in there that's relevant to today's code.
>
> But to answer your question: the entire kernel.softlockup.c file was removed in
> v2.6.36 because it had been replaced by entirely new code.
>

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-07-06  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05  7:34 There is "softlockup_tick()" function in the source code of linux-2.6.32, but what's the corresponding function name in the linux-4.9 or later? 孙世龙 sunshilong
2020-07-05 18:58 ` Valdis Klētnieks
2020-07-06  2:22   ` 孙世龙 sunshilong [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='CAAvDm6YzfOdgowkJVY8yRUdSX+Ou=V2KtasULm=sGdwbpWmC3w@mail.gmail.com' \
    --to=sunshilong369@gmail.com \
    --cc=Kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    /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;
as well as URLs for NNTP newsgroup(s).