From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Serge Noiraud <serge.noiraud@bull.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PREEMPT_RT : 2.6.16-rt12 and boot : BUG ?
Date: Wed, 12 Apr 2006 08:25:59 +0200 [thread overview]
Message-ID: <20060412062559.GB8499@elte.hu> (raw)
In-Reply-To: <1144807126.26133.21.camel@localhost.localdomain>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> > Why do we need such a size ?
>
> It seems that the -rt kernel has increased the size of structures that
> are used in modules and are defined per cpu.
i'm still wondering what that could be. The most drastic increase is the
size of locks (spinlocks, mutexes, etc.), especially with debugging
enabled - maybe one of the drivers uses a big per-CPU array of locks?
ah. One thing that takes up _alot_ of per-CPU space is the
latency-histogram stuff. I made the latency tracer itself use
non-per-cpu constructs to avoid overflowing the per-cpu-area, but the
latency-histogram code still uses PER_CPU:
#ifdef CONFIG_INTERRUPT_OFF_HIST
static DEFINE_PER_CPU(hist_data_t, interrupt_off_hist);
static char * interrupt_off_hist_proc_dir = "interrupt_off_latency";
#endif
#ifdef CONFIG_PREEMPT_OFF_HIST
static DEFINE_PER_CPU(hist_data_t, preempt_off_hist);
static char * preempt_off_hist_proc_dir = "preempt_off_latency";
#endif
#ifdef CONFIG_WAKEUP_LATENCY_HIST
static DEFINE_PER_CPU(hist_data_t, wakeup_latency_hist);
static char * wakeup_latency_hist_proc_dir = "wakeup_latency";
#endif
of a quite large array:
typedef struct hist_data_struct {
atomic_t hist_mode; /* 0 log, 1 don't log */
unsigned long min_lat;
unsigned long avg_lat;
unsigned long max_lat;
unsigned long long beyond_hist_bound_samples;
unsigned long long accumulate_lat;
unsigned long long total_samples;
unsigned long long hist_array[MAX_ENTRY_NUM];
} hist_data_t;
where MAX_ENTRY_NUM is 10240 right now. So the space used up is
10240*3*8 - roughly +256K per-cpu space!
I think that explains it. So the rule for -rt is, +256K more per-cpu
area is needed if the latency histograms are turned on.
Ingo
next prev parent reply other threads:[~2006-04-12 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 12:16 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 [this message]
2006-04-12 7:23 ` Serge Noiraud
2006-04-12 7:30 ` Serge Noiraud
2006-04-12 6:17 ` Ingo Molnar
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=20060412062559.GB8499@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
all inboxes | Powered by JetHome®