From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@wdc.com>,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v8 0/5] Initial support for multi-actuator HDDs
Date: Tue, 26 Oct 2021 18:45:33 -0600 [thread overview]
Message-ID: <173fe7e1-7e46-1827-5521-3e2648b85fcd@kernel.dk> (raw)
In-Reply-To: <20210909023545.1101672-1-damien.lemoal@wdc.com>
On 9/8/21 8:35 PM, Damien Le Moal wrote:
> 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.
Let's get this queued up for 5.16. I forgot what we agreed upon, can go
either block or SCSI. We likely have a bunch more block changes this
round than usual, and hence a higher risk of conflict, so from that
perspective alone I think the block layer would be easier.
In any case, Damien, it needs a respin as it doesn't apply against
my for-5.16/block at this point.
--
Jens Axboe
next prev parent reply other threads:[~2021-10-27 0:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 2:35 [PATCH v8 0/5] Initial support for multi-actuator HDDs Damien Le Moal
2021-09-09 2:35 ` [PATCH v8 1/5] block: Add independent access ranges support Damien Le Moal
2021-09-09 5:59 ` Hannes Reinecke
2021-09-09 2:35 ` [PATCH v8 2/5] scsi: sd: add concurrent positioning " Damien Le Moal
2021-09-09 6:00 ` Hannes Reinecke
2021-09-09 2:35 ` [PATCH v8 3/5] libata: support concurrent positioning ranges log Damien Le Moal
2021-09-09 2:35 ` [PATCH v8 4/5] doc: document sysfs queue/independent_access_ranges attributes Damien Le Moal
2021-09-09 2:35 ` [PATCH v8 5/5] doc: Fix typo in request queue sysfs documentation Damien Le Moal
2021-09-14 0:38 ` [PATCH v8 0/5] Initial support for multi-actuator HDDs Damien Le Moal
2021-09-27 9:17 ` Damien Le Moal
2021-09-29 3:55 ` Martin K. Petersen
2021-10-11 7:50 ` Damien Le Moal
2021-10-11 11:28 ` Tim Walker
2021-10-15 8:20 ` Damien Le Moal
2021-10-27 0:34 ` Keith Busch
2021-10-27 0:45 ` Jens Axboe [this message]
2021-10-27 0:49 ` Damien Le Moal
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=173fe7e1-7e46-1827-5521-3e2648b85fcd@kernel.dk \
--to=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.