public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Mark Salyzyn <mark_salyzyn@xyratex.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH][SCSI] enclosure & ses: modernize and add target power management (take 2)
Date: Wed, 22 Feb 2012 15:12:26 -0500	[thread overview]
Message-ID: <4F454C2A.7050806@interlog.com> (raw)
In-Reply-To: <48CA4310-FA29-4F54-9841-F25F12569FC6@xyratex.com>

On 12-02-22 02:09 PM, Mark Salyzyn wrote:
> Coincident repair of enclosure and ses device support. Fix problems with setting enclosure values careful to preserve other settings. Corrected fault setting as well. Modernize code. Add support for Device Power Management via a new r/w device_power node in sysfs and some internal interfaces to permit them to be called in the future by error recovery escalation. Enclosures that do not support individual power management will always return a status that the device has power.

Mark,
One problem I found with the existing kernel SES/enclosure
support is that it assumes there is a well-formed
Element Descriptor diagnostic page. By well-formed I mean that
the page exists and there is a unique, sensible entry for each
element. By sensible I mean _not_ like this:
   "TP=9C;SN=PMW82562000C39A;F1=0311;VR=03;VC=6B58AD13;PN=0082562-11;"

I have a SAS-2 expander with an associated SES device that breaks
all those tidy assumptions (i.e. I did not make up that string).
I assume that your patches do not change the reliance on a
well-formed Element Descriptor diagnostic page. Is the peculiar
SES device I have (and most SES-1 devices which don't have
Element Descriptor diagnostic pages) worth worrying about?

Doug Gilbert




  reply	other threads:[~2012-02-22 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23 23:48 [RFC] libsas: the trouble with ata resets Dan Williams
2011-10-26  3:04 ` Jack Wang
2011-11-11 16:14 ` [RFC] enclosure & ses: modernize and add target power management Mark Salyzyn
2011-11-11 21:33   ` Douglas Gilbert
2011-11-14 16:21     ` Mark Salyzyn
2012-01-12 17:03       ` [PATCH][SCSI] " Mark Salyzyn
2012-02-19 16:02         ` James Bottomley
2012-05-10 20:48           ` [PATCH][SCSI] panic within ses.ko during insmod Mark Salyzyn
2012-05-10 21:02             ` [PATCH][SCSI] panic within ses.ko during insmod (take 2) Mark Salyzyn
2012-05-11 19:08             ` [PATCH][SCSI] panic within ses.ko during insmod Dan Williams
2012-05-15  0:11               ` Mark Salyzyn
2012-02-22 19:09         ` [PATCH][SCSI] enclosure & ses: modernize and add target power management (take 2) Mark Salyzyn
2012-02-22 20:12           ` Douglas Gilbert [this message]
2012-02-22 20:40             ` Mark Salyzyn

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=4F454C2A.7050806@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@xyratex.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