From: Thomas Gleixner <tglx@linutronix.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Andi Kleen <ak@linux.intel.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
Yinghai Lu <yinghai@kernel.org>,
"Elliott, Robert (Server Storage)" <Elliott@hp.com>
Subject: Re: [PATCH 2/2 v2] x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs
Date: Wed, 4 Jun 2014 14:43:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1406041421370.3319@nanos> (raw)
In-Reply-To: <1400160305-17774-3-git-send-email-prarit@redhat.com>
On Thu, 15 May 2014, Prarit Bhargava wrote:
> +/* This array is used to keep track of how many empty vectors each cpu has. */
> +static int empty_vectors[NR_CPUS];
> +
No way! The whole vector accounting is a steaming pile of sh*t.
This needs to be fixed at the root of the problem, not by sh*tting on
top of the existing pile!
And the root of the problem is, that we do not have a uniform way to
access the empty vectors. Instead we have a bitmap, constants a
variable upper limit and the vector array. And you certainly noticed
that.
So why on earth are you trying to "fix" the issue by doing loops and
hoops on cpu unplug instead of doing a proper accounting in the first
place? It's all known prior to the point where you unplug a cpu.
FYI, don't try and add some crappy accounting hackery into the
existing vector allocation code. It's doomed.
Jiang is currently rewriting the ioapic code to use irq domains to
support physical ioapic hotplug. The next step is to move the
underlying vector allocation to irqdomains. When this happens we can
add the proper accounting.
That will allow us to support that unplug thing proper including
things like multi-MSI, which you cannot support with your bandaid
hackery at all.
Thanks,
tglx
prev parent reply other threads:[~2014-06-04 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 13:25 [PATCH 0/2 v2] x86, Fix irq exhaustion issues with cpu hotplug Prarit Bhargava
2014-05-15 13:25 ` [PATCH 1/2 v2] x86, irq: get correct available vectors for cpu disable Prarit Bhargava
2014-06-04 12:22 ` [tip:x86/urgent] x86: irq: Get " tip-bot for Yinghai Lu
2014-05-15 13:25 ` [PATCH 2/2 v2] x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs Prarit Bhargava
2014-06-04 12:43 ` Thomas Gleixner [this message]
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=alpine.DEB.2.10.1406041421370.3319@nanos \
--to=tglx@linutronix.de \
--cc=Elliott@hp.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®