SPC3: Application client page

Gerry.Houlder at seagate.com Gerry.Houlder at seagate.com
Wed Jul 18 21:43:17 PDT 2001


* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*

I agree that this page is provided/ saved on a per logical unit basis. This
is the traditional scope of mode pages and log pages.

This log page has a pretty large minimum size. This is intended so that a
lot of operating system and application information can be saved. It is
possible to reserve some records for target stuff and others for LUN stuff.
Another way to manage it would be to use LUN 0 for target stuff (plus the
stuff for that LUN) and not put target stuff on any other LUN.





JP Raghavendra Rao <Jp.Raghavendra at sun.com>@t10.org on 07/18/2001 02:03:08
PM

Please respond to JP Raghavendra Rao <Jp.Raghavendra at sun.com>

Sent by:  owner-t10 at t10.org


To:   t10 at t10.org
cc:

Subject:  SPC3: Application client page


* From the T10 Reflector (t10 at t10.org), posted by:
* JP Raghavendra Rao <Jp.Raghavendra at Sun.COM>
*

Traditionally log (sense/select) pages support information
stored at a device (target) or at a per logical unit granularity
at a conceptual level.

Now about the newly introduced "Application client page (0x0F)"
there is no mechanism to save/retrieve application data at the
device (target) level exclusively. The application data saved/retrieved
using this page seems to be on a per logical unit basis, although
no such explicit wording exists in the spec.

Comments ?

Thanks.
-JP

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org



*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list