From: Thorsten Leemhuis <regressions@leemhuis.info>
To: dedekind1@gmail.com, 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: Mon, 26 Mar 2018 10:39:25 +0200 [thread overview]
Message-ID: <ff7c4fd9-1685-05b9-8082-676aa4ae921d@leemhuis.info> (raw)
In-Reply-To: <1520515113.20980.31.camel@gmail.com>
Lo! Your friendly Linux regression tracker here ;-)
On 08.03.2018 14:18, Artem Bityutskiy wrote:
> On Thu, 2018-03-08 at 18:53 +0800, Ming Lei wrote:
>> 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.
> […]
> Tested-by: Artem Bityutskiy <artem.bityutskiy@intel.com>
> Link: https://lkml.kernel.org/r/1519311270.2535.53.camel@intel.com
>
> 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.
Artem (or anyone else), what's the status here? I have this on my list
of regressions, but it looks like there wasn't any progress in the past
week. Or was it discussed somewhere else or even fixed in the meantime
and I missed it? Ciao, Thorsten
next prev parent reply other threads:[~2018-03-26 8:39 UTC|newest]
Thread overview: 48+ 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 ` [PATCH V3 0/4] genirq/affinity: irq vector spread among online " Artem Bityutskiy
2018-03-08 13:25 ` 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 7:38 ` Artem Bityutskiy
2018-03-13 8:35 ` Ming Lei
2018-03-13 8:39 ` Artem Bityutskiy
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 [this message]
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=ff7c4fd9-1685-05b9-8082-676aa4ae921d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=axboe@kernel.dk \
--cc=dedekind1@gmail.com \
--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 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.