From: Sai Prajeeth <csprajeeth@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] OpenBSD sched_yield() calls increase
Date: Fri, 5 Jun 2015 16:33:23 +0530 [thread overview]
Message-ID: <CAFJamtOWVYTiYa4GGY8PvJi-5S5eNJ6zEPwt7EdiWiKo7YsO4w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Hi list,
When running OpenBSD on QEMU without KVM, I see an increase in the number
of sched_yield() system calls in certain multi-threaded benchmarks
(sysbench). However while using KVM accelerator, the number of this system
calls is minimal. Does any have any insight why this is happening? The
execution of the benchmark is really slowed when not using KVM which is to
be expected but why is there such as massive increase in sched_yield system
calls? Moreover when using icount the number of sched_yield calls is
further increased.
Some Number:
With KVM accelerator - #of sched_yields = 500
Using TCG - #of sched_yields = 2600
Using icount - #of sched_yields = 16000
Anyone has an idea why this might be happening?
Thank you!
[-- Attachment #2: Type: text/html, Size: 911 bytes --]
reply other threads:[~2015-06-05 11:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFJamtOWVYTiYa4GGY8PvJi-5S5eNJ6zEPwt7EdiWiKo7YsO4w@mail.gmail.com \
--to=csprajeeth@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).