Linux block layer
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
	 Zakaria Belkadi <zakaria.belkadi@inria.fr>,
	 Caleb Sander Mateos <csander@purestorage.com>,
	 Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org,
	 Kanchan Joshi <joshi.k@samsung.com>,
	 Anuj Gupta <anuj20.g@samsung.com>,
	florence.schadle@ssi.gouv.fr,
	 frederic.tronel@centralesupelec.fr, louis.rilling@irisa.fr,
	 stable@vger.kernel.org,  "Martin K. Petersen" <mkp@kernel.org>
Subject: Re: [PATCH RESEND] block: pin user PI pages for writing when ref tags are remapped
Date: Fri, 20 Nov 2026 22:14:21 -0500	[thread overview]
Message-ID: <yq18q2mnb36.fsf@mail.kernel.org> (raw)
In-Reply-To: <awB_xd60To4UawrJ@infradead.org>


Christoph,

> We could fine tune based on if we need remapping due to partitions, if
> we limited remapping to partitions, but I think Martin last time
> voiced an opinion that remapping could also be used to pass in
> arbitrary tags (which always felt a bit odd to me).

The application has no way of knowing what the first ref tag should be
except in cases where it is writing directly to a single block device.
Once the storage configuration involves multiple devices, or when
writing to a file, the concept of the user-visible ref tag being
LBA-based goes out the window. All the application knows is that it is
writing to block N of a given file.

That's why we then allow the application to pass in the seed value to
validate the PI against. Just like DIX and ILBRT/EILBRT, except this
particular translation happens at the application-kernel boundary.

-- 
Martin K. Petersen

      parent reply	other threads:[~2026-11-21  3:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 15:40 [PATCH RESEND] block: pin user PI pages for writing when ref tags are remapped Zakaria Belkadi
2026-11-19 22:44 ` Caleb Sander Mateos
2026-11-20 15:28 ` Christoph Hellwig
2026-11-20 16:22   ` Zakaria Belkadi
2026-11-20 16:58     ` Keith Busch
2026-11-20 17:13       ` Christoph Hellwig
2026-11-20 17:23         ` Keith Busch
2026-11-20 17:30           ` Christoph Hellwig
2026-11-20 17:44           ` Caleb Sander Mateos
2026-11-20 18:37             ` Keith Busch
2026-11-21  3:14         ` Martin K. Petersen [this message]

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=yq18q2mnb36.fsf@mail.kernel.org \
    --to=mkp@kernel.org \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=florence.schadle@ssi.gouv.fr \
    --cc=frederic.tronel@centralesupelec.fr \
    --cc=hch@infradead.org \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louis.rilling@irisa.fr \
    --cc=stable@vger.kernel.org \
    --cc=zakaria.belkadi@inria.fr \
    /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