From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org, Laurence Oberman <loberman@redhat.com>
Subject: Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible
Date: Thu, 08 Mar 2018 15:18:33 +0200 [thread overview]
Message-ID: <1520515113.20980.31.camel@gmail.com> (raw)
In-Reply-To: <20180308105358.1506-1-ming.lei@redhat.com>
On Thu, 2018-03-08 at 18:53 +0800, Ming Lei wrote:
> Hi,
>
> This patchset tries to spread among online CPUs as far as possible, so
> that we can avoid to allocate too less irq vectors with online CPUs
> mapped.
>
> For example, in a 8cores system, 4 cpu cores(4~7) are offline/non present,
> on a device with 4 queues:
>
> 1) before this patchset
> irq 39, cpu list 0-2
> irq 40, cpu list 3-4,6
> irq 41, cpu list 5
> irq 42, cpu list 7
>
> 2) after this patchset
> irq 39, cpu list 0,4
> irq 40, cpu list 1,6
> irq 41, cpu list 2,5
> irq 42, cpu list 3,7
>
> Without this patchset, only two vectors(39, 40) can be active, but there
> can be 4 active irq vectors after applying this patchset.
Tested-by: Artem Bityutskiy <artem.bityutskiy@intel.com>
Link: https://lkml.kernel.org/r/1519311270.2535.53.camel@intel.com
Ming,
this patchset fixes the v4.16-rcX regression that I reported few weeks
ago. I applied it and verified that Dell R640 server that I mentioned
in the bug report boots up and the disk works.
So this is not just an improvement, it also includes a bugfix.
Thanks!
next prev parent reply other threads:[~2018-03-08 13:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 10:53 [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible Ming Lei
2018-03-08 10:53 ` [PATCH V3 1/4] genirq/affinity: rename *node_to_possible_cpumask as *node_to_cpumask Ming Lei
2018-04-06 21:52 ` [tip:irq/core] genirq/affinity: Rename " tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 2/4] genirq/affinity: move actual irq vector spread into one helper Ming Lei
2018-04-06 21:53 ` [tip:irq/core] genirq/affinity: Move actual irq vector spreading into a helper function tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 3/4] genirq/affinity: support to do irq vectors spread starting from any vector Ming Lei
2018-04-06 21:53 ` [tip:irq/core] genirq/affinity: Allow irq spreading from a given starting point tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible Ming Lei
2018-04-03 13:32 ` Thomas Gleixner
2018-04-03 16:00 ` Ming Lei
2018-04-04 8:25 ` Thomas Gleixner
2018-04-04 12:45 ` Thomas Gleixner
2018-04-04 15:20 ` Ming Lei
2018-04-05 10:12 ` Thomas Gleixner
2018-04-04 15:08 ` Ming Lei
2018-04-04 19:38 ` Thomas Gleixner
2018-04-06 9:13 ` Ming Lei
2018-04-06 9:46 ` Thomas Gleixner
2018-04-06 21:49 ` Thomas Gleixner
2018-04-08 3:19 ` Ming Lei
2018-04-06 21:54 ` [tip:irq/core] genirq/affinity: Spread irq vectors among present " tip-bot for Ming Lei
2018-03-08 13:18 ` Artem Bityutskiy [this message]
2018-03-08 13:25 ` [PATCH V3 0/4] genirq/affinity: irq vector spread among online " Artem Bityutskiy
2018-03-08 13:34 ` Ming Lei
2018-03-08 23:20 ` Thomas Gleixner
2018-03-09 1:24 ` Ming Lei
2018-03-09 7:00 ` Artem Bityutskiy
2018-03-09 7:33 ` Ming Lei
2018-03-09 10:08 ` Thomas Gleixner
2018-03-09 12:08 ` Ming Lei
2018-03-09 15:08 ` Thomas Gleixner
2018-03-13 3:11 ` Dou Liyang
2018-03-13 7:38 ` Artem Bityutskiy
2018-03-13 8:35 ` Ming Lei
2018-03-13 8:39 ` Artem Bityutskiy
2018-03-13 9:35 ` Rafael J. Wysocki
2018-03-14 3:29 ` Dou Liyang
2018-03-14 4:11 ` Dou Liyang
2018-03-14 9:07 ` Artem Bityutskiy
2018-03-14 9:47 ` Dou Liyang
2018-03-13 9:25 ` Rafael J. Wysocki
2018-03-14 3:30 ` Dou Liyang
2018-03-30 3:15 ` Ming Lei
2018-04-03 12:55 ` Thomas Gleixner
2018-03-26 8:39 ` Thorsten Leemhuis
2018-03-28 6:15 ` Artem Bityutskiy
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=1520515113.20980.31.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=tglx@linutronix.de \
/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