mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nick Piggin <npiggin@suse.de>
Cc: Sachin Sant <sachinp@in.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	cl@linux-foundation.org, heiko.carstens@de.ibm.com,
	mingo@elte.hu, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] SLQB: Mark the allocator as broken PowerPC and S390
Date: Thu, 17 Sep 2009 14:43:38 +0300	[thread overview]
Message-ID: <84144f020909170443y5f8c3c8fo7d2a4163e636f368@mail.gmail.com> (raw)
In-Reply-To: <20090917113837.GK18404@wotan.suse.de>

Hi Nick,

Mel Gorman wrote:
>> >I have access to a ppc machine but not necessarily one with a memoryless
>> >nodes
>> >that can reproduce this problem.
>> >
>> >Assuming Sachin is the reporter and we are in the same company, maybe I
>> >have access to the machine. Sachin, can you mail me privately what this
>> >machine is called and lets see can I get some time on that machine? By
>> >any chance, was this bisected or did it just show up when SLQB became
>> >the default?

On Thu, Sep 17, 2009 at 04:53:41PM +0530, Sachin Sant wrote:
>> Have sent you the access details for the machine. This bug showed
>> up when SLQB was enabled as default in linux-next

On Thu, Sep 17, 2009 at 2:38 PM, Nick Piggin <npiggin@suse.de> wrote:
> Maybe it will be better to hold off merging until this is
> debugged then? If it is merged as a non-default option, then
> I can't see it being a huge issue to merge it a bit after the
> window? It doesn't touch anything else...

Me sending anything but bug fixes to Linus after the merge window is
closed...? That's one scary thought!

But yeah, I can hold the pull request until the issue is resolved. If
Linus doesn't want to merge SLQB for 2.6.32, we'll just try again for
2.6.33.

                        Pekka

  reply	other threads:[~2009-09-17 11:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  6:37 Pekka Enberg
2009-09-16  6:55 ` David Rientjes
2009-09-16  7:01   ` Pekka Enberg
2009-09-16  8:04     ` Heiko Carstens
2009-09-17 10:08 ` Mel Gorman
2009-09-17 10:29   ` Pekka Enberg
2009-09-17 10:57     ` Mel Gorman
2009-09-17 11:13       ` Pekka Enberg
2009-09-17 11:18         ` Mel Gorman
2009-09-17 11:23           ` Pekka Enberg
2009-09-17 11:41           ` Nick Piggin
2009-09-17 18:18             ` Mel Gorman
2009-09-17 18:28               ` Nick Piggin
2009-09-17 18:38                 ` Christoph Lameter
2009-09-17 18:51                   ` Nick Piggin
2009-09-18 15:56                 ` Mel Gorman
2009-09-17 11:23       ` Sachin Sant
2009-09-17 11:38         ` Nick Piggin
2009-09-17 11:43           ` Pekka Enberg [this message]
2009-09-17 11:52             ` Nick Piggin
2009-09-17 11:55               ` Pekka Enberg
2009-09-17 12:12       ` Heiko Carstens
2009-09-17 12:16         ` Pekka Enberg
2009-09-17 12:21           ` Heiko Carstens
2009-09-17 12:36             ` Nick Piggin
2009-09-17 12:42               ` Pekka Enberg

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=84144f020909170443y5f8c3c8fo7d2a4163e636f368@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=sachinp@in.ibm.com \
    --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

all inboxes | Powered by JetHome®