public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>,
	Alexander Viro <viro@ftp.linux.org.uk>
Cc: tytso@mit.edu, Alex Buell <alex.buell@munted.org.uk>,
	Mailing Lists - Kernel Developers  <linux-kernel@vger.kernel.org>,
	Eric Paris <eparis@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: Article in Phoronix about loss of performance in 2.6.35 release candidates
Date: Tue, 1 Jun 2010 08:17:49 +0200	[thread overview]
Message-ID: <20100601061749.GA26705@elte.hu> (raw)
In-Reply-To: <AANLkTikRoff0zK-o8W4Wb_MveGibxlOG8mnrQMBtYZOY@mail.gmail.com>


* Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> On Tue, Jun 1, 2010 at 7:10 AM,  <tytso@mit.edu> wrote:
> > On Tue, Jun 01, 2010 at 12:19:29AM +0100, Alex Buell wrote:
> >> http://www.phoronix.com/vr.php?view=14976
> >>
> >> Question: Why?
> >
> > One of the theories that has been advanced is that it's simply this
> > problem:
> >
> > ? ? ? ?http://lkml.org/lkml/2010/5/22/154
> >
> > If so, it points out how idiotic Phoronix is about not being able to
> > notice udev pegging the CPU at 100% being someone bad for its
> > benchmark runs. ?:-)
> >
> > OTOH, this bug has been known for over a week, and it is sort sad that
> > we haven't reverted this patch. ?It looks like the conversation has
> > died, but without a fix?
> 
> It's fixed by 1eb2cbb6d5efe129 so the problem doesn't exist for 2.6.35-r1.

Btw., the changelog in 1eb2cbb6d5efe129:

 | From 1eb2cbb6d5efe129cd006691267ce513c0aa59da Mon Sep 17 00:00:00 2001
 | From: Al Viro <viro@zeniv.linux.org.uk>
 | Date: Thu, 27 May 2010 11:11:06 -0400
 | Subject: [PATCH] Revert "anon_inode: set S_IFREG on the anon_inode"
 | 
 | This reverts commit a7cf4145bb86aaf85d4d4d29a69b50b688e2e49d.
 | ---
 |  fs/anon_inodes.c |    2 +-
 |  1 files changed, 1 insertions(+), 1 deletions(-)

Is lacking pretty much all essential pieces of information which are required 
for reverts:

 - it has no description about who reported the bug.

 - it has no description about what the problem was and what the effects were. 
   People have little chance to link up the 'udev is spinning' bug to
   this fix.

 - it has no link back to '3836a03: anon_inodes: mark the anon inode private' 
   which introduced it and hence it has no -stable tag either.

 - has no signoff line

	Ingo

  reply	other threads:[~2010-06-01  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 23:19 Article in Phoronix about loss of performance in 2.6.35 release candidates Alex Buell
2010-05-31 23:39 ` Robert Hancock
2010-06-01  0:46   ` Alex Buell
2010-06-01  0:52     ` Dave Airlie
2010-06-01  3:15   ` Bill Davidsen
2010-06-01  3:22     ` Robert Hancock
2010-06-01  5:38       ` Mike Galbraith
2010-06-01  4:10 ` tytso
2010-06-01  5:00   ` Pekka Enberg
2010-06-01  6:17     ` Ingo Molnar [this message]
2010-06-01  6:25       ` Ingo Molnar
2010-06-01  6:53       ` Ingo Molnar
2010-06-01 12:44     ` Chris Mason
2010-06-01  6:35   ` Ingo Molnar

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=20100601061749.GA26705@elte.hu \
    --to=mingo@elte.hu \
    --cc=alex.buell@munted.org.uk \
    --cc=arjan@infradead.org \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --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