From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched: high-res preemption tick
Date: Sat, 13 Oct 2007 10:55:17 +0200 [thread overview]
Message-ID: <1192265717.27435.44.camel@twins> (raw)
In-Reply-To: <1192259938.7369.4.camel@Homer.simpson.net>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Sat, 2007-10-13 at 09:18 +0200, Mike Galbraith wrote:
> On Fri, 2007-10-12 at 22:51 +0200, Peter Zijlstra wrote:
> > Subject: sched: high-res preemption tick
> >
> > Use HR-timers (when available) to deliver an accurate preemption tick.
>
> This patch further reduced iperf context switching, and boosted
> throughput.
>
> iperf -c localhost -P 10 -t 300
>
> Previously reported numbers
>
> 2.6.23-smp
> [SUM] 0.0-300.0 sec 153 GBytes 4.39 Gbits/sec
> [SUM] 0.0-300.1 sec 148 GBytes 4.23 Gbits/sec
> [SUM] 0.0-300.0 sec 152 GBytes 4.36 Gbits/sec
>
> 2.6.23-smp-d (sched-devel)
> [SUM] 0.0-300.0 sec 173 GBytes 4.96 Gbits/sec
> [SUM] 0.0-300.1 sec 173 GBytes 4.96 Gbits/sec
> [SUM] 0.0-300.0 sec 172 GBytes 4.93 Gbits/sec
>
> Numbers from fresh pull today
>
> 2.6.23-smp-d-hrt
> (re-enable PREEMPT_RESTRICT)
Ah, but HRTICK is not compatible with PREEMPT_RESTRICT, it will be
similar to !WAKEUP_PREEMPT.
> [SUM] 0.0-300.1 sec 181 GBytes 5.19 Gbits/sec
> [SUM] 0.0-300.0 sec 182 GBytes 5.22 Gbits/sec
> [SUM] 0.0-300.1 sec 182 GBytes 5.22 Gbits/sec
>
> 2.6.23-smp-d
> [SUM] 0.0-300.1 sec 174 GBytes 4.97 Gbits/sec
> [SUM] 0.0-300.1 sec 173 GBytes 4.95 Gbits/sec
> [SUM] 0.0-300.1 sec 173 GBytes 4.96 Gbits/sec
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-13 8:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:51 [PATCH] sched: high-res preemption tick Peter Zijlstra
2007-10-13 7:18 ` Mike Galbraith
2007-10-13 8:55 ` Peter Zijlstra [this message]
2007-10-13 9:17 ` Peter Zijlstra
2007-10-13 10:11 ` Mike Galbraith
2007-10-13 23:13 ` Peter Zijlstra
2007-10-13 23:16 ` Peter Zijlstra
2007-10-14 6:34 ` Mike Galbraith
2007-10-13 22:51 ` [RFC][PATCH] sched: SCHED_FIFO watchdog timer Peter Zijlstra
2007-10-15 13:26 ` Dmitry Adamushko
2007-10-15 13:57 ` Peter Zijlstra
2007-10-15 14:25 ` Lennart Poettering
2007-10-15 21:32 ` Kay Sievers
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=1192265717.27435.44.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox