From: Ming Lei <ming.lei@redhat.com>
To: Scotty Bauer <sbauer@eng.utah.edu>
Cc: linux-block@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
linux-nvme@lists.infradead.org, Linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] KPTI effect on IO performance
Date: Thu, 1 Feb 2018 11:05:52 +0800 [thread overview]
Message-ID: <20180201030551.GE23923@ming.t460p> (raw)
In-Reply-To: <d6729ac299e153de259cb8f8af0c888b@eng.utah.edu>
On Wed, Jan 31, 2018 at 11:43:33AM -0700, Scotty Bauer wrote:
> On 2018-01-31 01:23, Ming Lei wrote:
> > Hi All,
> >
> > After KPTI is merged, there is extra load introduced to context switch
> > between user space and kernel space. It is observed on my laptop that
> > one
> > syscall takes extra ~0.15us[1] compared with 'nopti'.
> >
> > IO performance is affected too, it is observed that IOPS drops by 32% in
> > my test[2] on null_blk compared with 'nopti':
> >
> > randread IOPS on latest linus tree:
> > -------------------------------------------------
> > | randread IOPS | randread IOPS with 'nopti'|
> > ------------------------------------------------
> > | 928K | 1372K |
> > ------------------------------------------------
> >
> >
>
> Do you know if your CPU has PCID? It would be interesting to see these tests
> on older CPUs or older kernels without PCID support.
BTW, I also saw test data in case of vCPU without PCID, and it is said the syscall
time can be close to ~30X compared with nopti, and the test should be setup easily
by adjust CPU model of Qemu.
So in case of no PCID, KPTI effect on IO performance should be much bigger than the
above data.
Thanks,
Ming
next prev parent reply other threads:[~2018-02-01 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:23 [LSF/MM TOPIC] KPTI effect on IO performance Ming Lei
2018-01-31 18:43 ` Scotty Bauer
2018-02-01 2:35 ` Ming Lei
2018-02-01 3:05 ` Ming Lei [this message]
2018-02-01 21:51 ` Bart Van Assche
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=20180201030551.GE23923@ming.t460p \
--to=ming.lei@redhat.com \
--cc=Linux-scsi@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sbauer@eng.utah.edu \
/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