All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Sébastien Dugué" <sebastien.dugue@bull.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: preempt-rt, NUMA and strange latency traces
Date: Wed, 8 Feb 2006 11:25:00 +0100	[thread overview]
Message-ID: <20060208102500.GA10942@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.58.0602080436190.8578@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> >   I've been experimenting with 2.6.15-rt16 on a dual 2.8GHz Xeon box
> > with quite good results and decided to make a run on a NUMA dual node
> > IBM x440 (8 1.4GHz Xeon, 28GB ram).
> >
> >   However, the kernel crashes early when creating the slabs. Does the
> > current preempt-rt patchset supports NUMA machines or has support
> > been disabled until things settle down?
> 
> Yeah, currently the -rt patch doesn't work well with NUMA.

FYI, i've got a new port of upstream slab.c to -rt, which should work on 
NUMA too. It'll be in -rt17 (later today or tomorrow).

	Ingo

  reply	other threads:[~2006-02-08 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 11:28 preempt-rt, NUMA and strange latency traces Sébastien Dugué
2006-02-08  9:41 ` Steven Rostedt
2006-02-08 10:25   ` Ingo Molnar [this message]
2006-02-08 10:47     ` Sébastien Dugué
2006-02-08 10:45   ` Sébastien Dugué
2006-02-08 16:49     ` john stultz
2006-02-09 11:11       ` Sébastien Dugué
2006-02-09 11:26         ` Sébastien Dugué
2006-02-09 18:54         ` john stultz
2006-02-10 13:07           ` Sébastien Dugué
2006-02-10 19:07             ` Lee Revell
2006-02-09  6:04     ` Lee Revell
2006-02-09 11:24       ` Sébastien Dugué
2006-02-09 20:02         ` Lee Revell
2006-02-10 13:18           ` Sébastien Dugué

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=20060208102500.GA10942@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sebastien.dugue@bull.net \
    /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.