setting nvme irq per cpu affinity in device driver

[김경산]

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 at 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?