From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: move ->ia_ranges from the request_queue to the gendisk
Date: Wed, 29 Jun 2022 09:22:39 +0200 [thread overview]
Message-ID: <20220629072239.GA20215@lst.de> (raw)
In-Reply-To: <36d397c2-3cfd-4872-1baa-f375d50aa6ba@opensource.wdc.com>
On Wed, Jun 29, 2022 at 04:08:29PM +0900, Damien Le Moal wrote:
> On 6/29/22 15:20, Christoph Hellwig wrote:
> > Independent access ranges only matter for file system I/O and are only
> > valid with a registered gendisk, so move them there.
>
> Would this potentially affect the use of ranges in DM ? E.g. exposing a
> dm-linear device targets as ranges. I do not think so but I did not check
> the details.
Device mapper only ever does file system I/O. Passthrough I/O must
be initiated by the actual driver like scsi or nvme.
next prev parent reply other threads:[~2022-06-29 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 6:20 clean up the blk-ia-ranges.c code a bit Christoph Hellwig
2022-06-29 6:20 ` [PATCH 1/2] block: move ->ia_ranges from the request_queue to the gendisk Christoph Hellwig
2022-06-29 7:08 ` Damien Le Moal
2022-06-29 7:22 ` Christoph Hellwig [this message]
2022-06-29 8:35 ` Damien Le Moal
2022-06-29 6:20 ` [PATCH 2/2] block: simplify disk_set_independent_access_ranges Christoph Hellwig
2022-06-29 8:37 ` Damien Le Moal
2022-06-29 6:32 ` clean up the blk-ia-ranges.c code a bit Damien Le Moal
2022-06-29 6:44 ` Christoph Hellwig
2022-06-29 6:52 ` Damien Le Moal
2022-06-29 8:38 ` Damien Le Moal
2022-06-29 14:36 ` Jens Axboe
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=20220629072239.GA20215@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-block@vger.kernel.org \
/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