public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. mattock" <justinmattock@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34-rc4
Date: Mon, 12 Apr 2010 19:42:10 -0700	[thread overview]
Message-ID: <4BC3DA02.2020208@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004121859480.3647@i5.linux-foundation.org>

On 04/12/2010 07:16 PM, Linus Torvalds wrote:
>
> It's been two weeks rather than the usual one, because we've been hunting
> a really annoying VM regression that not a lot of people seem to have
> seen, but I didn't want to release an -rc4 with it. So we had the choice
> of either reverting all the anon-vma scalability improvements, or finding
> out exactly what caused the regression and fixing it.
>
> And we got pretty close to the point where I was going to just revert it
> all.
>
> Absolutely _huge_ kudos to Borislav Petkov who reported the problem and
> was able to not just reliably reproduce it, but also test new patches to
> try to narrow things down at a moments notice. The thing took ten days of
> emails flying back and forth, and Borislav was there all the time, day and
> night, through several patches that tried to fix it (several real bugs,
> but not the one he hit) and lots of patches to just add instrumentation to
> get us nearer to the cause of the problem.
>
> And finally, today, confirmation that we actually nailed the problem. So
> if anybody has been seeing a oops (or sometimes a GP fault) in
> page_referenced(), that should be gone now.
>
> Anyway, there's certainly been other things going on too, but the VM
> regression was the one that kept me personally busy, and held up the
> release.
>
> The bulk of the changes come from drivers - a new network driver (cxgb4),
> but also updates to the radeon and nouveau drivers.
>
> And then there is the random updates everywhere. The appended shortlog is
> about as good an overview as anything.
>
> 		Linus
>
> ---


I noticed the vm discussion, but had no idea what was going on.
In any case that's pretty cool to see(read). Love to see the hard
work and collaboration to fix a problem.

cheers,

Justin P. Mattock

  reply	other threads:[~2010-04-13  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  2:16 Linux 2.6.34-rc4 Linus Torvalds
2010-04-13  2:42 ` Justin P. mattock [this message]
2010-04-14  8:38 ` Tobias
2010-04-14 14:46   ` Linus Torvalds
2010-04-14 20:47     ` Len Brown
2010-04-14 21:05       ` Tobias
2010-04-14 21:32     ` Harald Arnesen

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=4BC3DA02.2020208@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox