From: ks0204.kim@samsung.com (김경산)
Subject: setting nvme irq per cpu affinity in device driver
Date: Wed, 09 Sep 2015 09:35:08 +0900 [thread overview]
Message-ID: <006501d0ea97$6174cbf0$245e63d0$@samsung.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1509081446250.23840@localhost.lm.intel.com>
Actually, That's true.
Even though driver sets affinity during queue initialization, irqbalance
overwrite the setting when it run.
So, My suggestion is remain this feature for those who need to archieve
high IOPS with a direction exposed like something below.
-disable irqbalance
-insmod nvme.ko use_set_irq_affinity=1
-optionally, enable irqbalance again with -i option lists, nvme irq lists
monitoring banned
-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces@lists.infradead.org] On Behalf
Of Keith Busch
Sent: Tuesday, September 08, 2015 11:48 PM
To: ???
Cc: 'Christoph Hellwig'; Linux-nvme at lists.infradead.org
Subject: RE: setting nvme irq per cpu affinity in device driver
On Sun, 6 Sep 2015, ??? wrote:
> Hi Christoph Hellwig,
>
> I'd like to know the plan to provide the API from irq sybsystem.
> Let me kindly ask you to how can I get to know the status.
> Do you think should I need to contact to the irq maintainer?
I think it'd be great to propose to the irq subsystem, but I think this
doesn't necessarilly solve the problem. Won't irqbalance still undo
whatever the driver requested?
next prev parent reply other threads:[~2015-09-09 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 10:26 setting nvme irq per cpu affinity in device driver 김경산
2015-09-02 14:05 ` Christoph Hellwig
2015-09-03 5:01 ` 김경산
2015-09-06 8:06 ` 김경산
2015-09-07 17:54 ` 'Christoph Hellwig'
2015-09-10 10:25 ` 김경산
2015-09-08 14:47 ` Keith Busch
2015-09-09 0:35 ` 김경산 [this message]
2015-09-02 19:07 ` Keith Busch
2015-09-03 0:33 ` 김경산
2015-09-03 14:14 ` Keith Busch
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='006501d0ea97$6174cbf0$245e63d0$@samsung.com' \
--to=ks0204.kim@samsung.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