From: David Laight <David.Laight@ACULAB.COM>
To: "'Thorsten Leemhuis'" <regressions@leemhuis.info>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
Christoph Hellwig <hch@lst.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Stefan Haberland <sth@linux.vnet.ibm.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Herring,
Jan-kristian Augustin" <jan-kristian.augustin.herring@intel.com>
Subject: RE: regression: SCSI/SATA failure
Date: Mon, 5 Mar 2018 14:41:24 +0000 [thread overview]
Message-ID: <3ccf46026ca74faea98d4a9cdce221f9@AcuMS.aculab.com> (raw)
In-Reply-To: <c405f270-1bea-d34e-259e-fd9f372a495c@leemhuis.info>
From: Thorsten Leemhuis
> Hi! On 22.02.2018 15:57, Artem Bityutskiy wrote:
> > On Thu, 2018-02-22 at 16:54 +0200, Artem Bityutskiy wrote:
> >> one of our test box Skylake servers does not boot with v4.16-rcX.
> >> Bisection lead us to this commit:
> >> 84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
> >> Reverting this single commit fixes the problem.
>
> Artem, is this issue still happening? I still have it in my list of
> regressions. Side note: I accidentally noticed people continue working
> in the area that 84676c1f21e8 touched; see
> https://marc.info/?l=linux-block&m=152021971313902&w=2 ("[PATCH V2 5/5]
> genirq/affinity: irq vector spread among online CPUs as far as
> possible"). I wonder if that might be related in any way. Ciao, Thorsten
Hmmm.... I can think of some workloads where you really don't want some
cpu taking any interrupts at all (well as few as possible).
Think of workloads where process affinities are used to ensure that only
a few specific processes run on certain cpus.
The last thing you want then is interrupt load sharing and/or per cpu
ethernet rings.
David
next prev parent reply other threads:[~2018-03-05 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 14:54 regression: SCSI/SATA failure Bityutskiy, Artem
2018-02-22 14:57 ` Artem Bityutskiy
2018-03-05 14:17 ` Thorsten Leemhuis
2018-03-05 14:41 ` David Laight [this message]
2018-02-26 9:40 ` Thorsten Leemhuis
2018-03-05 14:41 ` Artem Bityutskiy
2018-03-28 6:31 ` 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=3ccf46026ca74faea98d4a9cdce221f9@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=dedekind1@gmail.com \
--cc=hch@lst.de \
--cc=jan-kristian.augustin.herring@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=sth@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).