From: Jeremy Linton <jlinton@tributary.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Michael Christie <michaelc@cs.wisc.edu>,
Hannes Reinecke <hare@suse.de>,
Linux Scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Use a more selective error recovery strategy based on device capabilities
Date: Fri, 15 Feb 2013 09:17:20 -0600 [thread overview]
Message-ID: <511E5180.6000400@tributary.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402950D58F40@G9W0745.americas.hpqcorp.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/14/2013 5:42 PM, Elliott, Robert (Server Storage) wrote:
> Each logical unit is independent and is allowed to be different.
I was actually just thinking about the target reset and IT reset flags. Two
flags which affect the I_T not the I_T_L.
For the target reset its probably a small proportion of devices anyway, The
patch already disables target reset if the device is known to support lun reset.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRHlGAAAoJEL5i86xrzcy7Yz8IAKn3w6DnUkPxmasQXi0WljNB
eqBZHIZRx8gjpa6AOP0nBt+FDSmyrhE4vLOUFIiwpcql1jmJ6iwcT+Y4YHwi+GzC
sE/ZtB5UDad4RleXcZIBHJwVVFtW0oCya2jYxr2GQFIEz3EefrfwwXEqdeI85uTv
aLiKakEP6EDQur280T08R9UEpFHirUnhMKoCFsXjtB5T6u2XDRLLWXQ8hE5ILBnX
Mf5HmCF8g1EjOnCJOzcUlhRlDuQe17FcDHyaxPkl2f34Qr+gdPo9WW5Cz38V0RLX
UYqmZI/B1GX7rUaU+Xhc4aAkxq6547cWZUwRLdZ6M4osFZT6GBuw3iRBevzNXDs=
=/1pc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-15 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 18:19 [PATCH] Use a more selective error recovery strategy based on device capabilities Jeremy Linton
2013-02-12 20:57 ` Elliott, Robert (Server Storage)
2013-02-12 22:00 ` Jeremy Linton
2013-02-13 13:06 ` Hannes Reinecke
2013-02-13 15:46 ` Jeremy Linton
2013-02-14 2:43 ` Michael Christie
2013-02-14 20:57 ` Jeremy Linton
2013-02-14 23:42 ` Elliott, Robert (Server Storage)
2013-02-15 15:17 ` Jeremy Linton [this message]
2013-02-15 7:17 ` Hannes Reinecke
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=511E5180.6000400@tributary.com \
--to=jlinton@tributary.com \
--cc=Elliott@hp.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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