From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <jbottomley@parallels.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"hch@infradead.org" <hch@infradead.org>,
"dgilbert@interlog.com" <dgilbert@interlog.com>,
"jlinton@tributary.com" <jlinton@tributary.com>,
"kai.makisara@kolumbus.fi" <kai.makisara@kolumbus.fi>,
"kay@vrfy.org" <kay@vrfy.org>
Subject: Re: [PATCH 3/5] Add EVPD page 0x83 to sysfs
Date: Mon, 10 Mar 2014 21:52:03 +0100 [thread overview]
Message-ID: <531E25F3.6090102@suse.de> (raw)
In-Reply-To: <1394475897.2565.46.camel@dabdike.int.hansenpartnership.com>
On 03/10/2014 07:24 PM, James Bottomley wrote:
> On Mon, 2014-03-10 at 15:28 +0100, Hannes Reinecke wrote:
>> EVPD page 0x83 is used to uniquely identify the device.
>> So instead of having each and every program issue a separate
>> SG_IO call to retrieve this information it does make far more
>> sense to display it in sysfs.
>
> Christoph's suggestion of binary sysfs attributes for this rather than
> the text ones you have is better ... because your current ones are going
> to truncate when they run off the one page of data sysfs text attributes
> get (i.e. about 2k of vpd).
>
Yes, I thought of that, too.
I thought to remember that binary attributes are reserved for
firmware/hardware-dependent interfaces.
If that's not the case I'll be moving to a binary attribute here.
Will be resending the patchset.
What should happen with the first patch in the series, then?
When moving to a binary attribute the first patch isn't required
anymore; should I drop it or send as a separate patch?
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-03-10 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 14:28 [PATCHv8 0/5] Display EVPD pages in sysfs Hannes Reinecke
2014-03-10 14:28 ` [PATCH 1/5] scsi_sysfs: Implement 'is_visible' callback Hannes Reinecke
2014-03-10 14:28 ` [PATCH 2/5] scsi: Return VPD page length in scsi_vpd_inquiry() Hannes Reinecke
2014-03-12 21:14 ` Muthukumar R
2014-03-12 21:43 ` Douglas Gilbert
2014-03-12 23:21 ` Muthukumar R
2014-03-13 6:45 ` Hannes Reinecke
2014-03-10 14:28 ` [PATCH 3/5] Add EVPD page 0x83 to sysfs Hannes Reinecke
2014-03-10 18:24 ` James Bottomley
2014-03-10 20:52 ` Hannes Reinecke [this message]
2014-03-11 4:14 ` James Bottomley
2014-03-11 11:56 ` Hannes Reinecke
2014-03-11 10:55 ` James Bottomley
2014-03-13 1:53 ` Martin K. Petersen
2014-03-13 3:31 ` James Bottomley
2014-03-12 8:03 ` hch
2014-03-10 14:28 ` [PATCH 4/5] Add EVPD page 0x80 " Hannes Reinecke
2014-03-10 14:28 ` [PATCH 5/5] ses: Use vpd information from scsi_device Hannes Reinecke
2014-03-10 18:20 ` James Bottomley
2014-03-10 20:44 ` 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=531E25F3.6090102@suse.de \
--to=hare@suse.de \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=jlinton@tributary.com \
--cc=kai.makisara@kolumbus.fi \
--cc=kay@vrfy.org \
--cc=linux-scsi@vger.kernel.org \
/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.