RT wakeup woes in Linux 2.6.31.6 on Mac Mini

From: Greg Steuck
Date: Thu Nov 12 2009 - 18:52:53 EST


Hello kernel gurus,

I would appreciate some ideas about reducing wakeup latency for our
real time application. The write up below identifies 3 seemingly
different cases of our task not getting to run long after it is woken
up.

We have a real-timish requirement for feeding a hardware device on
time. To achieve this goal we run a userspace program with SCHED_FIFO
at priority 99. We also set CPU affinity with sys_sched_setaffinity
inside our driver program (rxtest) to get a dedicated core (#1). We
change the affinity of all user processes (i.e. non-kernel threads) on
the system to stay on the other core (#0). Then we ran a bunch of
experiments with wakeup ftrace tracer enabled. Here is the script we
ran:

sudo mount -t debugfs nodev /sys/kernel/debug
cd /sys/kernel/debug/tracing

while : ; do
sudo sh -c '
echo wakeup > current_tracer
echo 0 > tracing_max_latency
echo 2 > tracing_cpumask
echo 1 > tracing_enabled
chrt -f 99 ~/rxtest -logtostderr 2>&1
echo 0 > tracing_enabled
cat trace > ~/trace.$$'
done | tee ~/tracing-wakeup-latency

There was some decent disk activity to keep the machine busy while the
script was running (rsync copying kernel source directory). We ran the
experiment some 15000 times and observed the average wakeup latency of
about 276 microseconds. There are however a few outliers that would be
nice to understand.

Latency (us) Trace log file
612 trace.1029
900 trace.13653
922 trace.6039

The attachments at http://sites.google.com/a/nest.cx/public/rtwakeup
have machine configuration and full traces. Belows are excerpts from
the trace files:

% egrep '[+!]' trace.*
trace.1029: <idle>-0 1d.s. 0us : 0:140:R + [001]
1030: 0:S rxtest
trace.1029: <idle>-0 1.Nh. 80us+: mii_rw <-nv_update_linkspeed
trace.1029: <idle>-0 1.Nh. 85us+: delay_tsc <-__delay
trace.1029: <idle>-0 1.Nh. 97us+: delay_tsc <-__delay
trace.1029: <idle>-0 1.Nh. 109us+: delay_tsc <-__delay
trace.1029: <idle>-0 1.Nh. 120us+: delay_tsc <-__delay
...
trace.13653:kblockd/-65 1d.s. 0us : 65:115:R + [001]
13654: 0:S rxtest
trace.13653:kblockd/-65 1dN.. 130us+: kmem_cache_alloc
<-mempool_alloc_slab
trace.13653:kblockd/-65 1dN.. 132us+: blk_rq_map_sg <-scsi_init_sgtable
trace.13653:kblockd/-65 1dN.. 200us+: blk_rq_map_sg <-scsi_init_sgtable
trace.13653:kblockd/-65 1dN.. 264us+: ata_tf_to_fis <-ahci_qc_prep
trace.13653:kblockd/-65 1dN.. 289us+: blk_rq_map_sg <-scsi_init_sgtable
trace.13653:kblockd/-65 1dN.. 349us+: ata_tf_to_fis <-ahci_qc_prep
...
trace.6039: pdflush-5162 1d.s. 0us : 5162:120:R + [001]
6040: 0:S rxtest
trace.6039: pdflush-5162 1dN.. 61us+: idle_cpu <-irq_exit
trace.6039: pdflush-5162 1dN.. 130us!: idle_cpu <-irq_exit
trace.6039: pdflush-5162 1dN.. 273us!: idle_cpu <-irq_exit

Thanks
Greg
--
nest.cx is Gmail hosted, use PGP for anything private. Key:
http://tinyurl.com/ho8qg
Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/