From: Tim Chen <tim.c.chen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Subject: system call time increase when turning on CONFIG_PARAVIRT
Date: Fri, 02 Mar 2007 12:11:14 -0800 [thread overview]
Message-ID: <1172866274.4898.14.camel@localhost.localdomain> (raw)
With CONFIG_PARAVIRT turned on, I've found that time invoking
system_call jumped up quite a lot. Using TCP streaming test as a
workload and running on 32-bit 2.6.20 kernel, system_call goes up from
0.00025% all the way to 1.6% in the oprofile data. There is a drop of
about 4% in overall throughput for this particular workload.
With lmbench's null system call test, the call time goes up from 0.10
usec to 0.225 usec.
I'm testing on dual socket Intel core 2 processor running at 2.67 GHz
with 4 GB RAM.
Tim
next reply other threads:[~2007-03-02 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 20:11 Tim Chen [this message]
2007-03-02 21:54 ` system call time increase when turning on CONFIG_PARAVIRT Jeremy Fitzhardinge
2007-03-02 23:11 ` Tim Chen
2007-03-03 0:16 ` Jeremy Fitzhardinge
2007-03-03 7:00 ` Zachary Amsden
2007-03-08 0:02 ` Tim Chen
2007-03-08 0:55 ` Jeremy Fitzhardinge
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=1172866274.4898.14.camel@localhost.localdomain \
--to=tim.c.chen@linux.intel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox