public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Valdis.Kletnieks@vt.edu
Cc: Pavel Machek <pavel@ucw.cz>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	joe@perches.com, torvalds@linux-foundation.org,
	peterz@infradead.org, efault@gmx.de, akpm@linux-foundation.org,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org,
	Alexander Viro <viro@ftp.linux.org.uk>
Subject: Re: [tip:sched/urgent] sched: Restore printk sanity
Date: Sun, 27 Dec 2009 06:56:37 +0100	[thread overview]
Message-ID: <20091227055637.GA22315@elte.hu> (raw)
In-Reply-To: <5723.1261874741@localhost>


* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:

> On Fri, 25 Dec 2009 19:45:14 +0100, Ingo Molnar said:
> 
> >  - in the last stable kernel, v2.6.32, still more new printk()s were 
> >    introduced than pr_*() lines:
> > 
> >      $ git log -p v2.6.31..v2.6.32 | grep '^+.*\<pr_' | wc -l
> >      2016
> >      $ git log -p v2.6.31..v2.6.32 | grep '^+.*\<printk' | wc -l
> >      3531
> 
> Ahem. That's not introduced, that's 'added or modified'.

'introduced or modified', yes. In those 5500 lines less than ~20% are 
'modifications' (the rest is newly introduced).

> % git log -p v2.6.31..v2.6.32 | grep -C 5 '^+.*\<pr_' | head
> -        * In case of failure continue with no timer. */
> +       /* Test if the external timer can be actually used.
> +        * In case of failure continue without timer. */
>         if (unlikely((stmmac_open_ext_timer(dev, priv->tm)) < 0)) {
> -               pr_warning("stmmaceth: cannot attach the HW timer\n");
> +               pr_warning("stmmaceth: cannot attach the external timer.\n");
>                 tmrate = 0;
>                 priv->tm->freq = 0;
>                 priv->tm->timer_start = stmmac_no_timer_started;
>                 priv->tm->timer_stop = stmmac_no_timer_stopped;
> 
> Meanwhile, the fact that there's only about a 2-to-1 difference in patches 
> when there's a 6-to-1 difference in existing code tells me that 
> proportionally, there is *more* activity with pr_foo variants than printk.

Yet there's more printks in the kernel than a cycle ago, so without the trend 
changing, we've got an infinite supply of future 'conversion' patches.

> printk:  3531 hits in 61126 uses = 5.7% churn
> pr_foo: 2016 hits in 10861 uses = 18.5% churn

Peter's complaint was precisely that there's a lot of 'churn' for pr_*().

> The numbers need much deeper analysis to make any sort of real statistical 
> conclusion here...

If you are convinced that there's something else going on as well feel free to 
do deeper analysis. So, until some contrary numbers are posted i stay by my 
main conclusions.

Thanks,

	Ingo

  reply	other threads:[~2009-12-27  5:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 13:23 sched: restore sanity Peter Zijlstra
2009-12-20 14:27 ` Arjan van de Ven
2009-12-20 14:49 ` Ingo Molnar
2009-12-20 14:51   ` Peter Zijlstra
     [not found]     ` <236ccac0912200703g464912b1r421497ebf3b6ebc6@mail.gmail.com>
2009-12-20 15:05       ` San Mehat
2009-12-20 15:19         ` Peter Zijlstra
2009-12-20 15:28           ` Mike Galbraith
2009-12-20 15:36           ` San Mehat
2009-12-20 17:22           ` Joe Perches
2009-12-20 17:36             ` Peter Zijlstra
2009-12-20 17:50               ` Ingo Molnar
2009-12-20 17:57               ` Joe Perches
2009-12-20 17:37             ` Ingo Molnar
2009-12-20 18:17             ` Arjan van de Ven
2009-12-20 18:21               ` Joe Perches
2009-12-21  0:48                 ` Arjan van de Ven
2009-12-21  1:20                   ` Joe Perches
2009-12-22 10:11             ` Al Viro
2009-12-20 17:22   ` Joe Perches
2009-12-20 18:00 ` [tip:sched/urgent] sched: Restore printk sanity tip-bot for Peter Zijlstra
2009-12-20 20:36   ` Geert Uytterhoeven
2009-12-21 20:40   ` Valdis.Kletnieks
2009-12-25 13:26   ` Pavel Machek
2009-12-25 18:45     ` Ingo Molnar
2009-12-27  0:45       ` Valdis.Kletnieks
2009-12-27  5:56         ` Ingo Molnar [this message]
     [not found]     ` <1261756819.4937.216.camel@laptop>
2009-12-25 18:39       ` Joe Perches
2009-12-25 18:47       ` Pavel Machek
2009-12-20 18:06 ` tip-bot for Peter Zijlstra
2009-12-20 18:55   ` Joe Perches
2009-12-20 19:15     ` Ingo Molnar
2009-12-20 19:44       ` [PATCH] scripts/checkpatch.pl: Add WARN on printk format split on multiple lines Joe Perches
2009-12-20 20:10         ` Ingo Molnar
2009-12-20 22:12       ` [tip:sched/urgent] sched: Restore printk sanity tytso
2009-12-21  1:11         ` Joe Perches

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=20091227055637.GA22315@elte.hu \
    --to=mingo@elte.hu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=hpa@zytor.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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