Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ks0204.kim@samsung.com (김경산)
Subject: setting nvme irq per cpu affinity in device driver
Date: Sun, 06 Sep 2015 17:06:24 +0900	[thread overview]
Message-ID: <000001d0e87a$ec9905d0$c5cb1170$@samsung.com> (raw)
In-Reply-To: <20150902140517.GA9787@infradead.org>

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? 

-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces@lists.infradead.org] On Behalf
Of Christoph Hellwig
Sent: Wednesday, September 02, 2015 11:05 PM
To: ??????
Cc: Linux-nvme at lists.infradead.org
Subject: Re: setting nvme irq per cpu affinity in device driver

We'll need a proper API in the interrupt subsystem to set the affinity
instead of poking directly into the internals.  The irq subsystem
maintainer already indicated he's fine with adding suh an API in principle.
Please go ahead and propose something similar to your implementation, just
as an exported API in kernel/irq instead of inside the NVMe driver.

_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2015-09-06  8:06 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   ` 김경산 [this message]
2015-09-07 17:54     ` 'Christoph Hellwig'
2015-09-10 10:25       ` 김경산
2015-09-08 14:47     ` Keith Busch
2015-09-09  0:35       ` 김경산
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='000001d0e87a$ec9905d0$c5cb1170$@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