[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180621211529.GA27589@localhost.localdomain>
Date: Thu, 21 Jun 2018 15:15:29 -0600
From: Keith Busch <keith.busch@...el.com>
To: Bart Van Assche <Bart.VanAssche@....com>
Cc: "hch@....de" <hch@....de>,
"jianchao.w.wang@...cle.com" <jianchao.w.wang@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"josef@...icpanda.com" <josef@...icpanda.com>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>
Subject: Re: [PATCH 0/5]stop normal completion path entering a timeout req
On Thu, Jun 21, 2018 at 06:21:09PM +0000, Bart Van Assche wrote:
> That's not how the SCSI core works.
How does it work? Jianchao is advocating for holes in software
to ignore reacting to hardware events and force unnecessary error
escalation. Putting holes in kernel software can't possibly be our
only recourse.
Powered by blists - more mailing lists