From: Damien Le Moal <email@example.com>
To: Jens Axboe <firstname.lastname@example.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"Martin K . Petersen" <email@example.com>,
Subject: Re: [PATCH v9 0/5] Initial support for multi-actuator HDDs
Date: Wed, 27 Oct 2021 12:42:10 +0900 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2021/10/27 12:03, Jens Axboe wrote:
> On 10/26/21 8:49 PM, Damien Le Moal wrote:
>> On 2021/10/27 11:38, Jens Axboe wrote:
>>> On 10/26/21 8:22 PM, Damien Le Moal wrote:
>>>> From: Damien Le Moal <email@example.com>
>>>> Single LUN multi-actuator hard-disks are cappable to seek and execute
>>>> multiple commands in parallel. This capability is exposed to the host
>>>> using the Concurrent Positioning Ranges VPD page (SCSI) and Log (ATA).
>>>> Each positioning range describes the contiguous set of LBAs that an
>>>> actuator serves.
>>>> This series adds support to the scsi disk driver to retreive this
>>>> information and advertize it to user space through sysfs. libata is
>>>> also modified to handle ATA drives.
>>>> The first patch adds the block layer plumbing to expose concurrent
>>>> sector ranges of the device through sysfs as a sub-directory of the
>>>> device sysfs queue directory. Patch 2 and 3 add support to sd and
>>>> libata. Finally patch 4 documents the sysfs queue attributed changes.
>>>> Patch 5 fixes a typo in the document file (strictly speaking, not
>>>> related to this series).
>>>> This series does not attempt in any way to optimize accesses to
>>>> multi-actuator devices (e.g. block IO schedulers or filesystems). This
>>>> initial support only exposes the independent access ranges information
>>>> to user space through sysfs.
>>> I've applied 1/9 for now, as that clearly belongs in the block tree.
>>> Might be the cleanest if SCSI does a post tree that depends on
>>> for-5.16/block. Or I can apply it all as they are reviewed. Let me
>> Forgot: They are all reviewed, including Martin who sent a Reviewed-by for the
>> series, but not an Acked-by for patch 2. As for libata patch 3, obviously, this
>> is Acked-by me.
> Queued up 2-5 in the for-5.16/scsi-ma branch.
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2021-10-27 3:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 2:22 [PATCH v9 0/5] Initial support for multi-actuator HDDs Damien Le Moal
2021-10-27 2:22 ` [PATCH v9 1/5] block: Add independent access ranges support Damien Le Moal
2021-10-27 2:22 ` [PATCH v9 2/5] scsi: sd: add concurrent positioning " Damien Le Moal
2021-10-27 2:22 ` [PATCH v9 3/5] libata: support concurrent positioning ranges log Damien Le Moal
2021-11-02 10:40 ` Geert Uytterhoeven
2021-11-02 11:42 ` Damien Le Moal
2021-11-02 14:02 ` Geert Uytterhoeven
2021-11-04 6:20 ` Damien Le Moal
2021-10-27 2:22 ` [PATCH v9 4/5] doc: document sysfs queue/independent_access_ranges attributes Damien Le Moal
2021-10-27 2:22 ` [PATCH v9 5/5] doc: Fix typo in request queue sysfs documentation Damien Le Moal
2021-10-27 2:37 ` (subset) [PATCH v9 0/5] Initial support for multi-actuator HDDs Jens Axboe
2021-10-27 2:38 ` Jens Axboe
2021-10-27 2:46 ` Damien Le Moal
2021-10-27 2:52 ` Martin K. Petersen
2021-10-27 2:53 ` Damien Le Moal
2021-10-27 2:49 ` Damien Le Moal
2021-10-27 3:03 ` Jens Axboe
2021-10-27 3:42 ` Damien Le Moal [this message]
2021-10-27 3:03 ` (subset) " Jens Axboe
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).