All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-rdma@vger.kernel.org, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] IRQ affinity
Date: Mon, 12 Oct 2015 12:09:48 -0400	[thread overview]
Message-ID: <20151012160948.GD20210@thunk.org> (raw)
In-Reply-To: <20150715120708.GA24534@infradead.org>

Hi Christoph,

Do you think this is still an issue that would be worth discsussing at
the kernel summit as a technical topic?  If so, would you be willing
to be responsible for kicking off the discussion for this topic?

Thanks,

					- Ted



On Wed, Jul 15, 2015 at 05:07:08AM -0700, Christoph Hellwig wrote:
> Many years ago we decided to move setting of IRQ to core affnities to
> userspace with the irqbalance daemon.
> 
> These days we have systems with lots of MSI-X vector, and we have
> hardware and subsystem support for per-CPU I/O queues in the block
> layer, the RDMA subsystem and probably the network stack (I'm not too
> familar with the recent developments there).  It would really help the
> out of the box performance and experience if we could allow such
> subsystems to bind interrupt vectors to the node that the queue is
> configured on.
> 
> I'd like to discuss if the rationale for moving the IRQ affinity setting
> fully to userspace are still correct in todays world any any pitfalls
> we'll have to learn from in irqbalanced and the old in-kernel affinity
> code.
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

WARNING: multiple messages have this Message-ID (diff)
From: tytso@mit.edu (Theodore Ts'o)
Subject: [Ksummit-discuss] [TECH TOPIC] IRQ affinity
Date: Mon, 12 Oct 2015 12:09:48 -0400	[thread overview]
Message-ID: <20151012160948.GD20210@thunk.org> (raw)
In-Reply-To: <20150715120708.GA24534@infradead.org>

Hi Christoph,

Do you think this is still an issue that would be worth discsussing at
the kernel summit as a technical topic?  If so, would you be willing
to be responsible for kicking off the discussion for this topic?

Thanks,

					- Ted



On Wed, Jul 15, 2015@05:07:08AM -0700, Christoph Hellwig wrote:
> Many years ago we decided to move setting of IRQ to core affnities to
> userspace with the irqbalance daemon.
> 
> These days we have systems with lots of MSI-X vector, and we have
> hardware and subsystem support for per-CPU I/O queues in the block
> layer, the RDMA subsystem and probably the network stack (I'm not too
> familar with the recent developments there).  It would really help the
> out of the box performance and experience if we could allow such
> subsystems to bind interrupt vectors to the node that the queue is
> configured on.
> 
> I'd like to discuss if the rationale for moving the IRQ affinity setting
> fully to userspace are still correct in todays world any any pitfalls
> we'll have to learn from in irqbalanced and the old in-kernel affinity
> code.
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] IRQ affinity
Date: Mon, 12 Oct 2015 12:09:48 -0400	[thread overview]
Message-ID: <20151012160948.GD20210@thunk.org> (raw)
In-Reply-To: <20150715120708.GA24534@infradead.org>

Hi Christoph,

Do you think this is still an issue that would be worth discsussing at
the kernel summit as a technical topic?  If so, would you be willing
to be responsible for kicking off the discussion for this topic?

Thanks,

					- Ted



On Wed, Jul 15, 2015 at 05:07:08AM -0700, Christoph Hellwig wrote:
> Many years ago we decided to move setting of IRQ to core affnities to
> userspace with the irqbalance daemon.
> 
> These days we have systems with lots of MSI-X vector, and we have
> hardware and subsystem support for per-CPU I/O queues in the block
> layer, the RDMA subsystem and probably the network stack (I'm not too
> familar with the recent developments there).  It would really help the
> out of the box performance and experience if we could allow such
> subsystems to bind interrupt vectors to the node that the queue is
> configured on.
> 
> I'd like to discuss if the rationale for moving the IRQ affinity setting
> fully to userspace are still correct in todays world any any pitfalls
> we'll have to learn from in irqbalanced and the old in-kernel affinity
> code.
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  parent reply	other threads:[~2015-10-12 16:10 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 12:07 [Ksummit-discuss] [TECH TOPIC] IRQ affinity Christoph Hellwig
2015-07-15 12:07 ` Christoph Hellwig
2015-07-15 12:07 ` Christoph Hellwig
2015-07-15 12:07 ` Christoph Hellwig
2015-07-15 12:12 ` [Ksummit-discuss] " Thomas Gleixner
2015-07-15 12:12   ` Thomas Gleixner
2015-07-15 12:12   ` Thomas Gleixner
2015-07-15 12:12   ` Thomas Gleixner
2015-07-15 15:41   ` Bart Van Assche
2015-07-15 15:41     ` Bart Van Assche
2015-07-15 15:41     ` Bart Van Assche
2015-07-15 15:41     ` Bart Van Assche
2015-07-15 17:19     ` Keith Busch
2015-07-15 17:19       ` Keith Busch
2015-07-15 17:19       ` Keith Busch
2015-07-15 17:19       ` Keith Busch
2015-07-15 17:25       ` Jens Axboe
2015-07-15 17:25         ` Jens Axboe
2015-07-15 17:25         ` Jens Axboe
2015-07-15 17:25         ` Jens Axboe
2015-07-15 18:24         ` Sagi Grimberg
2015-07-15 18:24           ` Sagi Grimberg
2015-07-15 18:24           ` Sagi Grimberg
2015-07-15 18:48         ` Matthew Wilcox
2015-07-15 18:48           ` Matthew Wilcox
2015-07-15 18:48           ` Matthew Wilcox
2015-07-16  6:13           ` Michael S. Tsirkin
2015-07-16  6:13             ` Michael S. Tsirkin
2015-07-16  6:13             ` Michael S. Tsirkin
2015-07-16  6:13             ` Michael S. Tsirkin
2015-07-17 15:51           ` Thomas Gleixner
2015-07-17 15:51             ` Thomas Gleixner
2015-07-17 15:51             ` Thomas Gleixner
2015-07-17 15:51             ` Thomas Gleixner
2015-07-15 14:38 ` Christoph Lameter
2015-07-15 14:38   ` Christoph Lameter
2015-07-15 14:38   ` Christoph Lameter
2015-07-15 14:56 ` [Ksummit-discuss] " Marc Zyngier
2015-07-15 14:56   ` Marc Zyngier
2015-07-15 14:56   ` Marc Zyngier
2015-07-15 16:05 ` Michael S. Tsirkin
2015-07-15 16:05   ` Michael S. Tsirkin
2015-07-15 16:05   ` Michael S. Tsirkin
2015-07-15 16:05   ` Michael S. Tsirkin
2015-10-12 16:09 ` Theodore Ts'o [this message]
2015-10-12 16:09   ` Theodore Ts'o
2015-10-12 16:09   ` Theodore Ts'o
2015-10-12 18:41   ` Christoph Hellwig
2015-10-12 18:41     ` Christoph Hellwig
2015-10-14 15:56     ` Theodore Ts'o
2015-10-14 15:56       ` Theodore Ts'o
2015-10-14 15:56       ` Theodore Ts'o

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=20151012160948.GD20210@thunk.org \
    --to=tytso@mit.edu \
    --cc=hch@infradead.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.