From: "Paul Rolland" <rol@witbe.net>
To: "'Kristian Benoit'" <kbenoit@opersys.com>,
<linux-kernel@vger.kernel.org>
Cc: <paulmck@us.ibm.com>, <bhuey@lnxw.com>, <andrea@suse.de>,
<tglx@linutronix.de>, <karim@opersys.com>, <mingo@elte.hu>,
<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 and I-PIPE: the numbers, part 4
Date: Sat, 9 Jul 2005 11:01:24 +0200 [thread overview]
Message-ID: <200507090901.j6991PD22890@tag.witbe.net> (raw)
In-Reply-To: <42CF05BE.3070908@opersys.com>
Hello,
> "IRQ & hd" run:
> Measurements | Vanilla | preempt_rt | ipipe
> ---------------+-------------+----------------+-------------
> fork | 101us | 94us (-7%) | 103us (+2%)
> open/close | 2.9us | 2.9us (~) | 3.0us (+3%)
> execve | 366us | 370us (+1%) | 372us (+2%)
> select 500fd | 14.3us | 18.1us (+27%) | 14.5us (+1%)
> mmap | 794us | 654us (+18%) | 822us (+4%)
^^^^^^^^^^^^
You mean -18%, not +18% I think.
Just having a quick long at the numbers, it seems that now the "weak"
part in PREEMPT_RT is the select 500fd test.
Ingo, any idea about this one ?
Regards,
Paul
next prev parent reply other threads:[~2005-07-09 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 23:01 PREEMPT_RT and I-PIPE: the numbers, part 4 Kristian Benoit
2005-07-09 1:28 ` Karim Yaghmour
2005-07-09 7:19 ` Ingo Molnar
2005-07-09 15:39 ` Karim Yaghmour
2005-07-09 15:53 ` Karim Yaghmour
2005-07-09 15:53 ` Karim Yaghmour
2005-07-11 7:05 ` Ingo Molnar
2005-07-11 11:25 ` Karim Yaghmour
2005-07-09 17:22 ` Daniel Walker
2005-07-09 23:37 ` Bill Huey
2005-07-09 9:01 ` Paul Rolland [this message]
2005-07-09 14:47 ` Karim Yaghmour
2005-07-09 15:22 ` Ingo Molnar
2005-07-11 5:24 ` Ingo Molnar
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=200507090901.j6991PD22890@tag.witbe.net \
--to=rol@witbe.net \
--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=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox