From: Hannes Reinecke <hare@suse.de>
To: Dongdong Hao <doubled@leap-io-kernel.com>,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: dlemoal@kernel.org, hare@kernel.org, yjzhang@leap-io-kernel.com,
kezijie@leap-io-kernel.com, jzzhang@leap-io-kernel.com,
baikefan@leap-io-kernel.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] scsi: leapraid: standardize NCQ priority sysfs attributes
Date: Tue, 18 Aug 2026 11:52:12 +0200 [thread overview]
Message-ID: <bed9ae35-00e9-4819-9c35-ab2a905e6220@suse.de> (raw)
In-Reply-To: <20260814090526.395704-1-doubled@leap-io-kernel.com>
On 8/14/26 11:05 AM, Dongdong Hao wrote:
> Replace the earlier LeapRAID ncq_cmd_prio_enable attribute with the
> standard sas_ncq_prio_supported and sas_ncq_prio_enable names documented
> in Documentation/ABI/testing/sysfs-block-device, and rename the
> per-device NCQ priority state to match.
>
> The earlier ncq_cmd_prio_enable name has not yet been established as part
> of a released userspace ABI, so no compatibility alias is needed.
>
> For LeapRAID, sas_ncq_prio_enable is backed by the driver's per-device
> NCQ priority state and controls whether RT-class I/O requests are issued
> with command priority on supported SATA devices.
>
> Update leapraid.rst to describe the standard attribute names and paths,
> and clean up the surrounding RST text for consistency with kernel
> documentation style.
>
> Also switch the capability check from open-coded VPD page 0x89 parsing to
> sas_ata_ncq_prio_supported(), use kstrtobool() for the enable path, and
> expose the NCQ priority attributes only for SATA devices using LeapRAID's
> target-private SAS device state.
>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> Signed-off-by: Dongdong Hao <doubled@leap-io-kernel.com>
> ---
> Changes in v2:
> - Reflow commit message lines to fit within 75 columns.
> - No functional change.
>
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-08-18 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 9:05 [PATCH v2] scsi: leapraid: standardize NCQ priority sysfs attributes Dongdong Hao
2026-08-18 9:52 ` Hannes Reinecke [this message]
2026-08-24 1:58 ` Martin K. Petersen (Oracle)
2026-08-26 15:20 ` Martin K. Petersen (Oracle)
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=bed9ae35-00e9-4819-9c35-ab2a905e6220@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=baikefan@leap-io-kernel.com \
--cc=dlemoal@kernel.org \
--cc=doubled@leap-io-kernel.com \
--cc=hare@kernel.org \
--cc=jzzhang@leap-io-kernel.com \
--cc=kezijie@leap-io-kernel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yjzhang@leap-io-kernel.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