[lkml]   [2010]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Article in Phoronix about loss of performance in 2.6.35 release candidates
On Tue, Jun 01, 2010 at 08:00:39AM +0300, Pekka Enberg wrote:
> On Tue, Jun 1, 2010 at 7:10 AM, <> wrote:
> > On Tue, Jun 01, 2010 at 12:19:29AM +0100, Alex Buell wrote:
> >>
> >>
> >> Question: Why?
> >
> > One of the theories that has been advanced is that it's simply this
> > problem:
> >
> >
> >
> > 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.

When I first read this email, I thought it meant the test was done
on rc1, but reading the article:

To cut to the chase, between the 22nd and 24th of May there
looks to be at least one commit (though perhaps multiple based
upon the different data) within the Linus Torvalds 2.6 Git tree
that are negatively affecting many different server/desktop
benchmarks. We waited nearly a week to see if these regressions
would be organically caught and addressed, but they have not
been at least of the Linux 2.6 Git state as of 2010-05-26.

I'll give the udev fix a try w/the btrfs tests.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2010-06-01 14:55    [W:0.060 / U:0.036 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site