The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Mike Christie <michael.christie@oracle.com>,
	Wenchao Hao <haowenchao@huawei.com>,
	Steffen Maier <maier@linux.ibm.com>,
	linux-scsi@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Lee Duncan <lduncan@suse.com>, John Garry <john.garry@huawei.com>,
	Wu Bo <wubo40@huawei.com>, Feilong Lin <linfeilong@huawei.com>,
	zhangjian013@huawei.com
Subject: Re: [REQUEST DISCUSS]: speed up SCSI error handle for host with massive devices
Date: Mon, 4 Apr 2022 00:40:02 -0700	[thread overview]
Message-ID: <Ykqg0kr0F/yzk2XW@infradead.org> (raw)
In-Reply-To: <769bcd36-4818-8470-2daa-49ac5c05b33a@suse.de>

On Mon, Apr 04, 2022 at 07:28:00AM +0200, Hannes Reinecke wrote:
> But really, I'd rather get my EH rework in before we're start discussing
> modifying EH behaviour.

Full agreed.  We need to sort that mess out first.

  reply	other threads:[~2022-04-04  7:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  9:06 [REQUEST DISCUSS]: speed up SCSI error handle for host with massive devices Wenchao Hao
2022-03-29 10:56 ` Steffen Maier
2022-03-29 12:40   ` Wenchao Hao
2022-03-29 18:56     ` Hannes Reinecke
2022-03-30  9:11       ` Wenchao Hao
2022-03-30  9:32         ` Hannes Reinecke
2022-03-30 10:59           ` Wenchao Hao
2022-04-03 17:14             ` Mike Christie
2022-04-03 17:17               ` Mike Christie
2022-04-04  5:28                 ` Hannes Reinecke
2022-04-04  7:40                   ` Christoph Hellwig [this message]
2022-04-06  9:40                   ` Wenchao Hao
2023-10-12 14:50                     ` Hannes Reinecke
2023-10-12 16:09                       ` Wenchao Hao
2022-04-06 10:32                   ` Wenchao Hao
2022-04-06  9:40               ` Wenchao Hao

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=Ykqg0kr0F/yzk2XW@infradead.org \
    --to=hch@infradead.org \
    --cc=haowenchao@huawei.com \
    --cc=hare@suse.de \
    --cc=jejb@linux.ibm.com \
    --cc=john.garry@huawei.com \
    --cc=lduncan@suse.com \
    --cc=linfeilong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maier@linux.ibm.com \
    --cc=martin.petersen@oracle.com \
    --cc=michael.christie@oracle.com \
    --cc=wubo40@huawei.com \
    --cc=zhangjian013@huawei.com \
    /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