All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Karim Yaghmour <karim@opersys.com>
Cc: Kristian Benoit <kbenoit@opersys.com>,
	linux-kernel@vger.kernel.org, paulmck@us.ibm.com, bhuey@lnxw.com,
	andrea@suse.de, tglx@linutronix.de, pmarques@grupopie.com,
	bruce@andrew.cmu.edu, nickpiggin@yahoo.com.au, ak@muc.de,
	sdietrich@mvista.com, dwalker@mvista.com, hch@infradead.org,
	akpm@osdl.org, rpm@xenomai.org
Subject: Re: PREEMPT_RT vs ADEOS: the numbers, part 1
Date: Sat, 11 Jun 2005 20:15:28 +0200	[thread overview]
Message-ID: <20050611181528.GA15019@elte.hu> (raw)
In-Reply-To: <42AB2209.9080006@opersys.com>


* Karim Yaghmour <karim@opersys.com> wrote:

> Here's the .config for 2.6.12-rc4-RT-V0.7.47-08:

Thanks. These PREEMPT_RT debugging features should be disabled:

> CONFIG_DEBUG_PREEMPT=y
> CONFIG_WAKEUP_TIMING=y
> CONFIG_PREEMPT_TRACE=y
> CONFIG_LATENCY_TIMING=y
> CONFIG_RT_DEADLOCK_DETECT=y

they all cause significant overhead.

I'd also disable these two security options:

> CONFIG_AUDIT=y
> CONFIG_SECURITY=y

unless you are running an selinux-enabled environment.

i've had not that good experiences with HPET:

> CONFIG_HPET_TIMER=y
> CONFIG_HPET_EMULATE_RTC=y

so i'd disable it - but YMMV.

i'd also disable PAE and use CONFIG_NOHIGHMEM:

> CONFIG_HIGHMEM64G=y

unless you have more than 4GB of RAM. (if you have between 1GB and 4GB 
then use HIGHMEM4G)

then i'd disable stack-overflow checking as well:

> CONFIG_DEBUG_STACKOVERFLOW=y
> CONFIG_DEBUG_STACK_USAGE=y

since you are not running 4K stacks.

	Ingo

  reply	other threads:[~2005-06-11 18:18 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11  4:36 PREEMPT_RT vs ADEOS: the numbers, part 1 Kristian Benoit
2005-06-11  6:14 ` Nick Piggin
2005-06-11  9:15   ` Sven-Thorsten Dietrich
2005-06-11 14:15     ` Kristian Benoit
2005-06-12 15:48       ` Philippe Gerum
2005-06-11 14:39     ` Karim Yaghmour
2005-06-11 22:14       ` Philippe Gerum
2005-06-11 13:57   ` Kristian Benoit
2005-06-11 14:28   ` Zwane Mwaikambo
2005-06-11  7:08 ` Ingo Molnar
2005-06-11  7:44   ` Nick Piggin
2005-06-11  9:27     ` Sven-Thorsten Dietrich
2005-06-12 15:31       ` Philippe Gerum
2005-06-11 14:28     ` Kristian Benoit
2005-06-11 10:37   ` Ingo Molnar
2005-06-11 14:23     ` Kristian Benoit
2005-06-11 14:56       ` Ingo Molnar
2005-06-11 14:31   ` Karim Yaghmour
2005-06-11 14:52     ` Ingo Molnar
2005-06-11 14:52       ` Karim Yaghmour
2005-06-11 17:40       ` Karim Yaghmour
2005-06-11 18:15         ` Ingo Molnar [this message]
2005-06-11 18:34           ` Ingo Molnar
2005-06-11 22:27             ` Karim Yaghmour
2005-06-12 10:47           ` James R Bruce
2005-06-12 14:54             ` Ingo Molnar
2005-06-13  2:39               ` Kristian Benoit
2005-06-11 19:14 ` Ingo Molnar
2005-06-11 22:31   ` Karim Yaghmour
2005-06-12  6:11     ` Ingo Molnar
2005-06-12 15:26       ` Daniel Walker
2005-06-12 19:29       ` Karim Yaghmour
2005-06-12 20:59         ` Ingo Molnar
2005-06-13  0:45           ` Andrea Arcangeli
2005-06-13  1:20             ` Karim Yaghmour
2005-06-13  5:47               ` Ingo Molnar
2005-06-12 22:20     ` Andrea Arcangeli
2005-06-12 23:03       ` Sven-Thorsten Dietrich
2005-06-13  0:53         ` randy_dunlap
2005-06-13  1:12           ` Karim Yaghmour
2005-06-13  6:51           ` Sven-Thorsten Dietrich
2005-06-13 15:00     ` Ingo Molnar
2005-06-13 15:12       ` Kristian Benoit
2005-06-11 19:27 ` Ingo Molnar
2005-06-12  4:21   ` Karim Yaghmour
2005-06-11 20:14 ` Paul E. McKenney
2005-06-11 22:33   ` Karim Yaghmour
2005-06-12 20:36     ` Paul E. McKenney
2005-06-12 11:11 ` James R Bruce
2005-06-12 19:49   ` Karim Yaghmour
2005-06-13  2:32     ` Kristian Benoit

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=20050611181528.GA15019@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=bhuey@lnxw.com \
    --cc=bruce@andrew.cmu.edu \
    --cc=dwalker@mvista.com \
    --cc=hch@infradead.org \
    --cc=karim@opersys.com \
    --cc=kbenoit@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulmck@us.ibm.com \
    --cc=pmarques@grupopie.com \
    --cc=rpm@xenomai.org \
    --cc=sdietrich@mvista.com \
    --cc=tglx@linutronix.de \
    /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.