From: Alejandro Colomar <alx@kernel.org>
To: Don Brace <don.brace@microchip.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v3 09/10] smartpqi: add device attributes
Date: Sat, 30 Sep 2023 01:21:44 +0200 [thread overview]
Message-ID: <ytcsqleu53iwpn5gsjmmuoqz2cy5oegvvafwlwxn422bcn3a5e@ne3khvixxzuq> (raw)
In-Reply-To: <20230926191206.627678-10-don.brace@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 3574 bytes --]
On Tue, Sep 26, 2023 at 02:12:04PM -0500, Don Brace wrote:
> Add in some device level sysfs entry descriptions:
> lunid
> unique_id
> path_info
> raid_bypass_cnt
> sas_ncq_prio_enable
>
> These have already been provided by the driver.
>
> Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
> Reviewed-by: Scott Teel <scott.teel@microchip.com>
> Reviewed-by: Mike McGowen <mike.mcgowen@microchip.com>
> Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
> Signed-off-by: Don Brace <don.brace@microchip.com>
> ---
> man4/smartpqi.4 | 91 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
>
> diff --git a/man4/smartpqi.4 b/man4/smartpqi.4
> index 19708a01f531..3de8b0c97423 100644
> --- a/man4/smartpqi.4
> +++ b/man4/smartpqi.4
> @@ -356,6 +356,97 @@ $ \c
> 0
> .EE
> .in
> +.TP
> +.IR /sys/class/scsi_disk/c : b : t : l/device/lunid
> +The
> +.I lunid
> +attribute is read-only.
> +This attribute contains the SCSI LUN ID for the device.
> +.IP
> +For example:
> +.IP
> +.in +4n
> +.EX
> +$ \c
> +.B cat /sys/class/scsi_disk/13:1:0:3/device/lunid
> +0x0300004000000000
> +.EE
> +.in
> +.TP
> +.IR /sys/class/scsi_disk/c : b : t : l/device/unique_id
> +The
> +.I unique_id
> +attribute is read-only.
> +This attribute contains a 16-byte ID that uniquely identifies the device within the controller.
Please don't go past the 80-col limit.
> +.IP
> +For example:
> +.IP
> +.in +4n
> +.EX
> +$ \c
> +.B cat /sys/class/scsi_disk/13:1:0:3/device/unique_id
> +600508B1001C6D4723A8E98D704FDB94
> +.EE
> +.in
> +.TP
> +.IR /sys/class/scsi_disk/c : b : t : l/device/path_info
> +The
> +.I path_info
> +attribute is read-only.
> +This attribute contains the c:b:t:l of the device along with the device type and whether the device is Active or Inactive. If the device is an HBA device,
> +.I path_info
> +will also display the PORT, BOX, and BAY the device is plugged into.
> +.IP
> +For example:
> +.IP
> +.in +4n
> +.EX
> +$ \c
> +.B cat /sys/class/scsi_disk/13:1:0:3/device/path_info
> +[13:1:0:3] Direct-Access Active
> +
Blank lines in examples should use the dummy character \&
It prevents a groff(1) warning.
> +$ \c
> +.B cat /sys/class/scsi_disk/12:0:9:0/device/path_info
> +[12:0:9:0] Direct-Access PORT: C1 BOX: 1 BAY: 14 Inactive
> +[12:0:9:0] Direct-Access PORT: C0 BOX: 1 BAY: 14 Active
> +.EE
> +.in
> +.TP
> +.IR /sys/class/scsi_disk/13:1:0:3/device/raid_bypass_cnt
This should be .I.
Thanks,
Alex
> +The
> +.I raid_bypass_cnt
> +attribute is read-only.
> +This attribute contains the number of I/O requests that have gone through the
> +ioaccel path for ioaccel-enabled volumes. See the
> +.BI ssd_smart_path_enabled
> +disk attribute section for details on ioaccel-enabled volumes.
> +.IP
> +For example:
> +.IP
> +.in +4n
> +.EX
> +$ \c
> +.B cat /sys/class/scsi_disk/13:1:0:3/device/raid_bypass_cnt
> +0x300
> +.EE
> +.in
> +.TP
> +.IR /sys/class/scsi_disk/13:1:0:3/device/sas_ncq_prio_enable
> +The
> +.I sas_ncq_prio_enable
> +attribute is read/write.
> +This attribute enables SATA NCQ priority support.
> +This attribute works only when device has NCQ support and
> +controller firmware can handle IO with NCQ priority attribute.
> +.IP
> +For example:
> +.IP
> +.in +4n
> +.EX
> +$ \c
> +.B echo 1 > /sys/class/scsi_disk/13:1:0:3/device/sas_ncq_prio_enable
> +.EE
> +.in
> .SH VERSIONS
> The
> .B smartpqi
> --
> 2.42.0.158.g94e83dcf5b
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-29 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 19:11 [PATCH v3 00/10] smartpqi man page updates Don Brace
2023-09-26 19:11 ` [PATCH v3 01/10] smarpqi: update copyright and email addresses Don Brace
2023-09-26 23:40 ` Alejandro Colomar
2023-09-26 19:11 ` [PATCH v3 02/10] smartpqi: update module parameter descriptions Don Brace
2023-09-26 23:45 ` Alejandro Colomar
2023-09-26 19:11 ` [PATCH v3 03/10] smartpqi: add-module parameter disable_managed_interrupts Don Brace
2023-09-26 23:50 ` Alejandro Colomar
2023-09-27 14:38 ` Don.Brace
2023-09-26 19:11 ` [PATCH v3 04/10] smartpqi: add module parameter ctrl_ready_timeout Don Brace
2023-09-29 23:07 ` Alejandro Colomar
2023-09-26 19:12 ` [PATCH v3 05/10] smartpqi: update FILES section Don Brace
2023-09-29 23:16 ` Alejandro Colomar
2023-09-26 19:12 ` [PATCH v3 06/10] smartpqi: update host attribute descriptions Don Brace
2023-09-29 23:10 ` Alejandro Colomar
2023-10-02 16:32 ` Don.Brace
2023-10-02 17:28 ` Alejandro Colomar
2023-09-26 19:12 ` [PATCH v3 07/10] smartpqi: update device " Don Brace
2023-09-29 23:16 ` Alejandro Colomar
2023-09-26 19:12 ` [PATCH v3 08/10] smartpqi: add host attributes Don Brace
2023-09-29 23:19 ` Alejandro Colomar
2023-09-26 19:12 ` [PATCH v3 09/10] smartpqi: add device attributes Don Brace
2023-09-29 23:21 ` Alejandro Colomar [this message]
2023-09-26 19:12 ` [PATCH v3 10/10] smartpqi: add sg entry to see_also Don Brace
2023-09-29 23:22 ` Alejandro Colomar
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=ytcsqleu53iwpn5gsjmmuoqz2cy5oegvvafwlwxn422bcn3a5e@ne3khvixxzuq \
--to=alx@kernel.org \
--cc=don.brace@microchip.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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;
as well as URLs for NNTP newsgroup(s).