All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au, vatsa@in.ibm.com,
	suresh.b.siddha@intel.com, Simon.Derr@bull.net, steiner@sgi.com,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [BUG] sched: big numa dynamic sched domain memory corruption
Date: Mon, 31 Jul 2006 10:04:25 -0700	[thread overview]
Message-ID: <20060731100425.65432d31.pj@sgi.com> (raw)
In-Reply-To: <20060731090440.A2311@unix-os.sc.intel.com>

> Paul can you please test the mainline code and confirm?

This will take me a few hours - it requires a bit of
slab debugging scaffolding to detect the memory corruption
in a timely and accurate manner.  I'll have to port that
scaffolding forward from its current SLES10 base.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2006-07-31 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  7:07 [BUG] sched: big numa dynamic sched domain memory corruption Paul Jackson
2006-07-31  7:12 ` Ingo Molnar
2006-07-31 16:04   ` Siddha, Suresh B
2006-07-31 16:54     ` Paul Jackson
2006-07-31 17:15       ` Siddha, Suresh B
2006-08-02  6:57         ` Paul Jackson
2006-08-02 21:36           ` Siddha, Suresh B
2006-08-02 21:58             ` Paul Jackson
2006-08-06  1:38             ` Paul Jackson
2006-07-31 17:04     ` Paul Jackson [this message]
2006-08-01  8:25     ` Paul Jackson
2006-08-01 19:00       ` Siddha, Suresh B
2006-08-01 19:16         ` Paul Jackson

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=20060731100425.65432d31.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=steiner@sgi.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@in.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.