From: keith.busch@intel.com (Keith Busch)
Subject: Extremely high context switches of i/o to NVM
Date: Fri, 24 Jul 2015 20:27:16 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1507242006210.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <2140969145.2200151.1437768000851.JavaMail.yahoo@mail.yahoo.com>
On Fri, 24 Jul 2015, Junjie Qian wrote:
> Hi List,
>
> I run experiment with NVM on NUMA, and found the context switch is extremely high.
>
> The platform is, 1. Linux 4.1-rc7 with multi-queue enabled, kernel is polling enabled (5 secs polling, but the results show little difference between polling and interrupt); 2. 4-socket NUMA machine; 3. Intel PC3700 NVM
>
> The command is sudo perf state -e context-switches nice -n -20 numactl -C 0 fio-master/fio --name=1 --bs=4k --ioengine=libaio --iodepth=1 --rw=read --numjobs=1 --filename=/dev/nvme0n1 --thread --direct=1 --group_reporting --time_based=1 --runtime=60
>
> The result is 3,567,428 context switches.
>
> Would someone give me some help on explaining this? Is this reasonable?
> Thanks!
Sounds about right with an IO depth of 1. You're going to get a context
switch per IO, right?
next prev parent reply other threads:[~2015-07-24 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 20:00 Extremely high context switches of i/o to NVM Junjie Qian
2015-07-24 20:27 ` Keith Busch [this message]
2015-07-24 23:03 ` Junjie Qian
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=alpine.LNX.2.00.1507242006210.15930@localhost.lm.intel.com \
--to=keith.busch@intel.com \
/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