From: John Sigler <linux.kernel@free.fr>
To: Alessio Igor Bogani <abogani@texware.it>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Pin-pointing the root of unusual application latencies
Date: Wed, 25 Jul 2007 16:35:03 +0200 [thread overview]
Message-ID: <46A75F97.8000103@free.fr> (raw)
In-Reply-To: <1185372808.23485.2.camel@godzilla.tecnorama.it>
Alessio Igor Bogani wrote:
> John Sigler wrote:
>
>> # cat /proc/interrupts
>> CPU0
>> 0: 37 XT-PIC-XT timer
>
> Just curious: Can you post the output of the "cat /proc/timer_list" ?
Kernel command line: [...] lpj=12667000 lapic nmi_watchdog=0 idle=halt
Kernel configuration:
http://linux.kernel.free.fr/latency/config-2.6.20.7-rt8-adlink-latency
# cat /proc/timer_list
Timer List Version: v0.3
HRTIMER_MAX_CLOCK_BASES: 2
now at 3759145433320 nsecs
cpu: 0
clock 0:
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 1185370134437814624 nsecs
active timers:
clock 1:
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: <cf795e74>, tick_sched_timer, S:01
# expires at 3759150000000 nsecs [in 4566680 nsecs]
#1: <cf795e74>, it_real_fn, S:01
# expires at 5027741374801 nsecs [in 1268595941481 nsecs]
.expires_next : 3759150000000 nsecs
.hres_active : 1
.nr_events : 375503
.nohz_mode : 0
.idle_tick : 0 nsecs
.tick_stopped : 0
.idle_jiffies : 0
.idle_calls : 0
.idle_sleeps : 0
.idle_entrytime : 0 nsecs
.idle_sleeptime : 0 nsecs
.last_jiffies : 0
.next_jiffies : 0
.idle_expires : 0 nsecs
jiffies: 345914
Tick Device: mode: 1
Clock Event Device: pit
max_delta_ns: 27461866
min_delta_ns: 12571
mult: 5124677
shift: 32
mode: 3
next_event: 9223372036854775807 nsecs
set_next_event: pit_next_event
set_mode: init_pit_timer
event_handler: tick_handle_oneshot_broadcast
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000
Tick Device: mode: 1
Clock Event Device: lapic
max_delta_ns: 1006582530
min_delta_ns: 1799
mult: 35793183
shift: 32
mode: 3
next_event: 3759150000000 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: hrtimer_interrupt
next prev parent reply other threads:[~2007-07-25 14:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 10:22 Pin-pointing the root of unusual application latencies John Sigler
2007-07-13 8:32 ` John Sigler
2007-07-23 8:25 ` John Sigler
2007-07-23 9:53 ` Ingo Molnar
2007-07-23 14:14 ` John Sigler
2007-07-23 16:04 ` Ingo Molnar
2007-07-23 16:04 ` Ingo Molnar
2007-07-23 16:44 ` John Sigler
2007-07-24 8:31 ` John Sigler
2007-07-24 9:20 ` John Sigler
2007-07-25 13:04 ` John Sigler
2007-07-25 13:05 ` Ingo Molnar
2007-07-25 13:05 ` Ingo Molnar
2007-07-25 13:20 ` John Sigler
2007-07-25 13:38 ` Ingo Molnar
2007-07-25 14:05 ` John Sigler
2007-07-25 14:13 ` Alessio Igor Bogani
2007-07-25 14:35 ` John Sigler [this message]
2007-07-25 15:00 ` Alessio Igor Bogani
2007-07-25 15:21 ` John Sigler
2007-07-25 15:35 ` Alessio Igor Bogani
2007-07-25 15:53 ` John Sigler
2007-07-25 15:28 ` Karsten Wiese
2007-07-25 15:46 ` John Sigler
2007-07-25 16:31 ` Karsten Wiese
2007-07-25 17:09 ` Len Brown
2007-07-26 8:35 ` John Sigler
2007-07-26 10:45 ` John Sigler
2007-07-26 12:02 ` John Sigler
2007-07-26 15:16 ` John Sigler
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=46A75F97.8000103@free.fr \
--to=linux.kernel@free.fr \
--cc=abogani@texware.it \
--cc=linux-rt-users@vger.kernel.org \
/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.