From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mikael Pettersson <mikpelinux@gmail.com>
Cc: Linux SPARC Kernel Mailing List <sparclinux@vger.kernel.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500
Date: Sun, 10 Feb 2019 07:44:32 -0800 [thread overview]
Message-ID: <1549813472.4142.3.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAM43=SPUMzOLRmkoT+DQSpzu2DYRTyOhU6o8KRUU_Q902o2e1Q@mail.gmail.com>
On Sun, 2019-02-10 at 10:17 +0100, Mikael Pettersson wrote:
> On Sat, Feb 9, 2019 at 7:19 PM James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
[...]
> > I think the reason for this is that the block mq path doesn't feed
> > the kernel entropy pool correctly, hence the need to install an
> > entropy gatherer for systems that don't have other good random
> > number sources.
>
> That does sound plausible, I admit I didn't even consider the
> possibility that the old block I/O path also was an entropy source.
In theory, the new one should be as well since the rotational entropy
collector is on the SCSI completion path. I'd seen the same problem
but had assumed it was something someone had done to our internal
entropy pool and thus hadn't bisected it.
James
next prev parent reply other threads:[~2019-02-10 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 17:04 [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500 Mikael Pettersson
2019-02-09 18:19 ` James Bottomley
2019-02-10 9:17 ` Mikael Pettersson
2019-02-10 15:44 ` James Bottomley [this message]
2019-02-10 16:05 ` Jens Axboe
2019-02-10 16:25 ` James Bottomley
2019-02-10 16:35 ` Jens Axboe
2019-02-11 15:25 ` James Bottomley
2019-02-11 15:28 ` Jens Axboe
2019-02-11 15:42 ` James Bottomley
2019-02-11 15:46 ` Jens Axboe
2019-02-11 16:28 ` James Bottomley
2019-02-11 16:31 ` Jens Axboe
2019-02-12 2:13 ` James Bottomley
2019-02-12 2:50 ` Jens Axboe
2019-02-12 3:37 ` Elliott, Robert (Persistent Memory)
2019-02-12 4:15 ` James Bottomley
2019-02-12 15:24 ` James Bottomley
2019-02-12 15:27 ` Jens Axboe
2019-02-14 18:35 ` Mikael Pettersson
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=1549813472.4142.3.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpelinux@gmail.com \
--cc=sparclinux@vger.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).