linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: PREEMPT_RT : 2.6.16-rt12 and boot : BUG ?
Date: Wed, 12 Apr 2006 08:17:15 +0200	[thread overview]
Message-ID: <20060412061715.GA8499@elte.hu> (raw)
In-Reply-To: <200604111815.25494.Serge.Noiraud@bull.net>


* Serge Noiraud <serge.noiraud@bull.net> wrote:

> Hi,
> 
> 	It now works with all config parameters set to yes on 2.6.16-rt16.
> however, PERCPU_ENOUGH_ROOM is set to 384KB.
> I'm now trying to lower this value of PERCPU_ENOUGH_ROOM.
> With 256K and 2.6.16-rt16 : doesn't work.
> With 320K : OK
> So I need to use 320K for PERCPU_ENOUGH_ROOM to boot correctly.

great detective work! I've increased it to 512K in my tree, to be on the 
safe side. I'm not sure which parameter takes so much per-cpu space.  
There's certainly no problem with your config, this must be something 
caused by the -rt tree. The -rt tree introduces a new per-cpu concept 
(called PER_CPU_LOCKED) which is used in a couple of cases, but it 
shouldnt cause this drastic increase of the per-cpu area's size. Weird.

	Ingo

  parent reply	other threads:[~2006-04-12  6:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 12:16 PREEMPT_RT : 2.6.16-rt12 and boot : BUG ? Serge Noiraud
2006-04-06 14:31 ` Ingo Molnar
2006-04-06 15:05   ` Serge Noiraud
2006-04-10 12:46     ` Serge Noiraud
2006-04-11 16:15       ` Serge Noiraud
2006-04-12  1:58         ` Steven Rostedt
2006-04-12  6:25           ` Ingo Molnar
2006-04-12  7:23             ` Serge Noiraud
2006-04-12  7:30           ` Serge Noiraud
2006-04-12  6:17         ` Ingo Molnar [this message]
2006-04-06 14:33 ` Aurelien Degremont
2006-04-06 15:10   ` Serge Noiraud
2006-04-07  9:39     ` Aurelien Degremont
2006-04-06 12:40 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=20060412061715.GA8499@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=serge.noiraud@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).