From: Christoph Hellwig <hch@lst.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Anuj Gupta <anuj20.g@samsung.com>, Christoph Hellwig <hch@lst.de>,
Kanchan Joshi <joshi.k@samsung.com>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: fine-grained PI control
Date: Tue, 24 Sep 2024 07:36:44 +0200 [thread overview]
Message-ID: <20240924053644.GA10569@lst.de> (raw)
In-Reply-To: <yq1bk0dhlko.fsf@ca-mkp.ca.oracle.com>
On Mon, Sep 23, 2024 at 09:59:10PM -0400, Martin K. Petersen wrote:
> Originally we had code in Linux allowing filesystems to attach
> additional metadata to bios which would then be stored in the app tag
> space. This was intended for backpointers but never really took off.
> However, if we move the burden of PI generation to filesystems as
> Christoph suggested, then we can revisit using the app tag space.
Just to make clear I want file systems to be able to opt into
generating PI, not get rid of the auto generation. That is actually
kinda possible already, I just want to make it nicer.
next prev parent reply other threads:[~2024-09-24 5:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 8:32 fine-grained PI control Christoph Hellwig
2024-07-08 14:17 ` Anuj gupta
2024-07-09 7:08 ` Christoph Hellwig
2024-07-09 3:35 ` Martin K. Petersen
2024-07-09 7:16 ` Christoph Hellwig
2024-07-10 3:47 ` Martin K. Petersen
2024-07-11 5:42 ` Christoph Hellwig
2024-07-16 2:07 ` Martin K. Petersen
2024-07-26 10:21 ` Anuj Gupta
2024-07-29 17:03 ` Christoph Hellwig
2024-09-18 6:39 ` Anuj Gupta
2024-09-24 1:59 ` Martin K. Petersen
2024-09-24 5:36 ` Christoph Hellwig [this message]
2024-09-27 2:01 ` Martin K. Petersen
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=20240924053644.GA10569@lst.de \
--to=hch@lst.de \
--cc=anuj20.g@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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.