From: Keith Busch <keith.busch@gmail.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Long Li <longli@microsoft.com>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
chenxiang <chenxiang66@hisilicon.com>,
Peter Zijlstra <peterz@infradead.org>,
Ming Lei <tom.leiming@gmail.com>,
John Garry <john.garry@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-nvme <linux-nvme@lists.infradead.org>,
Keith Busch <keith.busch@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
"longli@linuxonhyperv.com" <longli@linuxonhyperv.com>
Subject: Re: [PATCH 0/3] fix interrupt swamp in NVMe
Date: Wed, 21 Aug 2019 20:00:33 -0600 [thread overview]
Message-ID: <CAOSXXT7LVjBqVW14y-pZyUCat3PBPd_nVd_uDahBdhyW+eHmcg@mail.gmail.com> (raw)
In-Reply-To: <20190822013356.GC28635@ming.t460p>
On Wed, Aug 21, 2019 at 7:34 PM Ming Lei <ming.lei@redhat.com> wrote:
> On Wed, Aug 21, 2019 at 04:27:00PM +0000, Long Li wrote:
> > Here is the command to benchmark it:
> >
> > fio --bs=4k --ioengine=libaio --iodepth=128 --filename=/dev/nvme0n1:/dev/nvme1n1:/dev/nvme2n1:/dev/nvme3n1:/dev/nvme4n1:/dev/nvme5n1:/dev/nvme6n1:/dev/nvme7n1:/dev/nvme8n1:/dev/nvme9n1 --direct=1 --runtime=120 --numjobs=80 --rw=randread --name=test --group_reporting --gtod_reduce=1
> >
>
> I can reproduce the issue on one machine(96 cores) with 4 NVMes(32 queues), so
> each queue is served on 3 CPUs.
>
> IOPS drops > 20% when 'use_threaded_interrupts' is enabled. From fio log, CPU
> context switch is increased a lot.
Interestingly use_threaded_interrupts shows a marginal improvement on
my machine with the same fio profile. It was only 5 NVMes, but they've
one queue per-cpu on 112 cores.
next prev parent reply other threads:[~2019-08-22 2:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 6:14 [PATCH 0/3] fix interrupt swamp in NVMe longli
2019-08-20 6:14 ` [PATCH 1/3] sched: define a function to report the number of context switches on a CPU longli
2019-08-20 9:38 ` Peter Zijlstra
2019-08-21 8:20 ` Long Li
2019-08-21 10:34 ` Peter Zijlstra
2019-08-20 9:39 ` Peter Zijlstra
2019-08-20 6:14 ` [PATCH 2/3] sched: export idle_cpu() longli
2019-08-20 6:14 ` [PATCH 3/3] nvme: complete request in work queue on CPU with flooded interrupts longli
2019-08-20 9:52 ` Peter Zijlstra
2019-08-21 8:37 ` Long Li
2019-08-21 10:35 ` Peter Zijlstra
2019-08-20 17:33 ` Sagi Grimberg
2019-08-21 8:39 ` Long Li
2019-08-21 17:36 ` Long Li
2019-08-21 21:54 ` Sagi Grimberg
2019-08-24 0:13 ` Long Li
2019-08-23 3:21 ` Ming Lei
2019-08-24 0:27 ` Long Li
2019-08-24 12:55 ` Ming Lei
2019-08-20 8:25 ` [PATCH 0/3] fix interrupt swamp in NVMe Ming Lei
2019-08-20 8:59 ` John Garry
2019-08-20 15:05 ` Keith Busch
2019-08-21 7:47 ` Long Li
2019-08-21 9:44 ` Ming Lei
2019-08-21 10:03 ` John Garry
2019-08-21 16:27 ` Long Li
2019-08-22 1:33 ` Ming Lei
2019-08-22 2:00 ` Keith Busch [this message]
2019-08-22 2:23 ` Ming Lei
2019-08-22 9:48 ` Thomas Gleixner
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=CAOSXXT7LVjBqVW14y-pZyUCat3PBPd_nVd_uDahBdhyW+eHmcg@mail.gmail.com \
--to=keith.busch@gmail.com \
--cc=axboe@fb.com \
--cc=chenxiang66@hisilicon.com \
--cc=hch@lst.de \
--cc=john.garry@huawei.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=ming.lei@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sagi@grimberg.me \
--cc=tglx@linutronix.de \
--cc=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).