From: Hannes Reinecke <hare@suse.de>
To: Ren Mingxin <renmx@cn.fujitsu.com>
Cc: James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, Ewan Milne <emilne@redhat.com>
Subject: Re: [PATCH 7/8] scsi: Add 'eh_deadline' to limit SCSI EH runtime
Date: Fri, 28 Feb 2014 08:24:50 +0100 [thread overview]
Message-ID: <531039C2.5000307@suse.de> (raw)
In-Reply-To: <5310344D.8090400@cn.fujitsu.com>
On 02/28/2014 08:01 AM, Ren Mingxin wrote:
> Hi, Hannes:
>
> On 10/23/2013 04:51 PM, Hannes Reinecke wrote:
>> This patchs adds an 'eh_deadline' sysfs attribute to the scsi
>> host which limits the overall runtime of the SCSI EH.
>
> As you known, adding to scsi host means such interface has also been
> added to the SATA and USB controllers. But to users, I think it is
> possible that there are 3 confusing points below:
>
> 1) There should not be this sysfs interface for SATA controllers, for
> such interface will not work under SATA's own EH policy;
> 2) There should not be this sysfs interface for USB controllers,
> because probably they will not consider EH recovery to USB ones;
> 3) They are not willing to affect SATA/USB controllers(even if their
> sysfs interfaces) while setting global interafce by assigning scsi
> module parameter.
>
> I was thinking how to mask SATA/USB controllers, but havn't a perfect
> solution so far, for it seems that it is not clever enough to mask
> them in each controller driver. Do you have any idea about above?
>
Yes, I have.
I've send a patchset titled 'Display EVPD pages in sysfs', which
introduces the ability to mask individual (device) attributes.
The same mechanism can easily be used for host attributes.
James B indicated that those patches might be okay for inclusion,
but so far nothing has happened with them.
I'll ping him again.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-28 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 8:51 [PATCHv3 0/8] Limit overall SCSI EH runtime Hannes Reinecke
2013-10-23 8:51 ` [PATCH 1/8] dpt_i2o: Remove DPTI_STATE_IOCTL Hannes Reinecke
2013-10-23 8:51 ` [PATCH 2/8] dpt_i2o: return SCSI_MLQUEUE_HOST_BUSY when in reset Hannes Reinecke
2013-10-23 8:51 ` [PATCH 3/8] advansys: Remove 'last_reset' references Hannes Reinecke
2013-10-23 8:51 ` [PATCH 4/8] tmscsim: Move 'last_reset' into host structure Hannes Reinecke
2013-10-23 8:51 ` [PATCH 5/8] dc395: Move 'last_reset' into internal " Hannes Reinecke
2013-10-23 8:51 ` [PATCH 6/8] scsi: remove check for 'resetting' Hannes Reinecke
2013-10-23 8:51 ` [PATCH 7/8] scsi: Add 'eh_deadline' to limit SCSI EH runtime Hannes Reinecke
2013-10-23 9:30 ` Ren Mingxin
2014-02-28 7:01 ` Ren Mingxin
2014-02-28 7:24 ` Hannes Reinecke [this message]
2013-10-23 8:51 ` [PATCH 8/8] scsi_error: Escalate to LUN reset if abort fails Hannes Reinecke
2013-10-23 13:53 ` Ewan Milne
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=531039C2.5000307@suse.de \
--to=hare@suse.de \
--cc=emilne@redhat.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=renmx@cn.fujitsu.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 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.