From: GeHao Kang <kanghao0928@gmail.com>
To: fweisbec@gmail.com, cmetcalf@mellanox.com,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org,
paulmck@linux.vnet.ibm.com
Subject: Context switch latency in tickless isolated CPU
Date: Wed, 17 Aug 2016 14:26:10 +0800 [thread overview]
Message-ID: <CANv7uPR+RidX41Jyzy-xpYqYHSPiw3TrBgAm11PzOfNEeP7wJA@mail.gmail.com> (raw)
Hi Frederic and Chris,
When the lmbench runs on the tickless isolated CPU, the context switch
latency on
this CPU is higher than the one on other CPU. The test platform is
Linux 4.4.12 with NO_HZ_FULL on I.MX6Q sabresd. The following is the
lmbench results about context switch:
lmbench runs on nonspecific CPU:
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ------ ------ ------ ------ ------ ------- -------
imx6qsabr Linux 4.4.12- 12.6 12.8 16.1 26.6 42.1 36.5 70.0
lmbench runs on the isolated CPU:
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ------ ------ ------ ------ ------ ------- -------
imx6qsabr Linux 4.4.12- 17.7 21.9 27.6 42.0 40.3 44.0 77.1
>From the results, only the test case with 8p/64K on the isolated CPU
has lower latency.
To investigate the cause, I use the kernel event tracer to find out
the events, user_enter and user_exit, of context_tracking would happen
on tickless isolated CPU. These two events means that this CPU enters
and exits the RCU extended quiescent state. Besides, the execution
time of these two events are 3us and 2us,
which are measured by ktime. Is this the reason why the context switch
has higher
latency on the tickless isolated CPU?
Thanks,
Regards,
- Kang
next reply other threads:[~2016-08-17 6:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 6:26 GeHao Kang [this message]
2016-08-17 12:18 ` Context switch latency in tickless isolated CPU Chris Metcalf
2016-08-18 3:25 ` GeHao Kang
2016-08-19 12:34 ` Peter Zijlstra
2016-08-21 11:26 ` GeHao Kang
2016-08-21 14:53 ` Paul E. McKenney
2016-08-22 9:40 ` GeHao Kang
2016-08-22 14:48 ` Paul E. McKenney
2016-08-22 15:12 ` Mark Hounschell
2016-08-22 15:37 ` Paul E. McKenney
2016-08-22 16:35 ` Mark Hounschell
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=CANv7uPR+RidX41Jyzy-xpYqYHSPiw3TrBgAm11PzOfNEeP7wJA@mail.gmail.com \
--to=kanghao0928@gmail.com \
--cc=cmetcalf@mellanox.com \
--cc=fweisbec@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).