linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dou Liyang <dou_liyang@163.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, mingo@redhat.com,
	hpa@zytor.com, douly.fnst@cn.fujitsu.com
Subject: Re: [PATCH v3 2/2] irq/matrix: Spread managed interrupts on allocation
Date: Wed, 19 Sep 2018 00:02:51 +0800	[thread overview]
Message-ID: <d8f6c9d3-9947-a5ba-3b2b-b8625d2afeb5@163.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1809171713270.16580@nanos.tec.linutronix.de>

Dear Thomas,

On 2018/9/17 23:32, Thomas Gleixner wrote:
[...]
> I think it's still worthwhile to do that, but the changelog needs a major
> overhaul as right now it's outright misleading. I'll just amend it with
> something along the above lines, unless someone disagrees.
> 

Yeah, Yes, right, I was wrong, can't prevent vector exhaustion, just
make it looks balance as you said. Thank you so much.

> That said, it might also be interesting to allow user space affinity
> settings on managed interrupts. Not meant for the pre/post vector case,
> which just needs to be made non managed. It's meant for the case where a

Yes, I am cooking according to the direction you are proposing.
Recently, I changed my PC and just completed the configuration of the
environment. ;-)

Thanks,
	dou


  reply	other threads:[~2018-09-18 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 17:58 [PATCH v3 1/2] irq/matrix: Split out the CPU finding code into a helper Dou Liyang
2018-09-08 17:58 ` [PATCH v3 2/2] irq/matrix: Spread managed interrupts on allocation Dou Liyang
2018-09-17 15:32   ` Thomas Gleixner
2018-09-18 16:02     ` Dou Liyang [this message]
2018-09-18 16:37   ` [tip:x86/apic] " tip-bot for Dou Liyang
2018-09-18 16:36 ` [tip:x86/apic] irq/matrix: Split out the CPU selection code into a helper tip-bot for Dou Liyang

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=d8f6c9d3-9947-a5ba-3b2b-b8625d2afeb5@163.com \
    --to=dou_liyang@163.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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).