public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>, Christian Brauner <brauner@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Carlos Maiolino <cem@kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Anuj Gupta <anuj20.g@samsung.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	ntfs3@lists.linux.dev, linux-block@vger.kernel.org,
	nvdimm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: [PATCH 05/16] block: make max_integrity_io_size public
Date: Mon, 23 Feb 2026 05:20:05 -0800	[thread overview]
Message-ID: <20260223132021.292832-6-hch@lst.de> (raw)
In-Reply-To: <20260223132021.292832-1-hch@lst.de>

File systems that generate integrity will need this, so move it out
of the block private or blk-mq specific headers.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Tested-by: Anuj Gupta <anuj20.g@samsung.com>
---
 block/blk-settings.c          | 13 -------------
 include/linux/blk-integrity.h |  5 -----
 include/linux/blkdev.h        | 18 ++++++++++++++++++
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/block/blk-settings.c b/block/blk-settings.c
index a9e65dc090da..dabfab97fbab 100644
--- a/block/blk-settings.c
+++ b/block/blk-settings.c
@@ -123,19 +123,6 @@ static int blk_validate_zoned_limits(struct queue_limits *lim)
 	return 0;
 }
 
-/*
- * Maximum size of I/O that needs a block layer integrity buffer.  Limited
- * by the number of intervals for which we can fit the integrity buffer into
- * the buffer size.  Because the buffer is a single segment it is also limited
- * by the maximum segment size.
- */
-static inline unsigned int max_integrity_io_size(struct queue_limits *lim)
-{
-	return min_t(unsigned int, lim->max_segment_size,
-		(BLK_INTEGRITY_MAX_SIZE / lim->integrity.metadata_size) <<
-			lim->integrity.interval_exp);
-}
-
 static int blk_validate_integrity_limits(struct queue_limits *lim)
 {
 	struct blk_integrity *bi = &lim->integrity;
diff --git a/include/linux/blk-integrity.h b/include/linux/blk-integrity.h
index fd3f3c8c0fcd..ea6d7d322ae3 100644
--- a/include/linux/blk-integrity.h
+++ b/include/linux/blk-integrity.h
@@ -8,11 +8,6 @@
 
 struct request;
 
-/*
- * Maximum contiguous integrity buffer allocation.
- */
-#define BLK_INTEGRITY_MAX_SIZE		SZ_2M
-
 enum blk_integrity_flags {
 	BLK_INTEGRITY_NOVERIFY		= 1 << 0,
 	BLK_INTEGRITY_NOGENERATE	= 1 << 1,
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index dec0acaed6e6..11857ae13d10 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1881,6 +1881,24 @@ static inline int bio_split_rw_at(struct bio *bio,
 	return bio_split_io_at(bio, lim, segs, max_bytes, lim->dma_alignment);
 }
 
+/*
+ * Maximum contiguous integrity buffer allocation.
+ */
+#define BLK_INTEGRITY_MAX_SIZE		SZ_2M
+
+/*
+ * Maximum size of I/O that needs a block layer integrity buffer.  Limited
+ * by the number of intervals for which we can fit the integrity buffer into
+ * the buffer size.  Because the buffer is a single segment it is also limited
+ * by the maximum segment size.
+ */
+static inline unsigned int max_integrity_io_size(struct queue_limits *lim)
+{
+	return min_t(unsigned int, lim->max_segment_size,
+		(BLK_INTEGRITY_MAX_SIZE / lim->integrity.metadata_size) <<
+			lim->integrity.interval_exp);
+}
+
 #define DEFINE_IO_COMP_BATCH(name)	struct io_comp_batch name = { }
 
 #endif /* _LINUX_BLKDEV_H */
-- 
2.47.3


  parent reply	other threads:[~2026-02-23 13:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 13:20 support file system generated / verified integrity information v4 Christoph Hellwig
2026-02-23 13:20 ` [PATCH 01/16] block: factor out a bio_integrity_action helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 02/16] block: factor out a bio_integrity_setup_default helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 03/16] block: add a bdev_has_integrity_csum helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 04/16] block: prepare generation / verification helpers for fs usage Christoph Hellwig
2026-02-23 13:20 ` Christoph Hellwig [this message]
2026-02-23 13:20 ` [PATCH 06/16] block: add fs_bio_integrity helpers Christoph Hellwig
2026-02-23 13:20 ` [PATCH 07/16] block: pass a maxlen argument to bio_iov_iter_bounce Christoph Hellwig
2026-02-23 13:20 ` [PATCH 08/16] iomap: refactor iomap_bio_read_folio_range Christoph Hellwig
2026-02-23 13:20 ` [PATCH 09/16] iomap: pass the iomap_iter to ->submit_read Christoph Hellwig
2026-02-23 13:20 ` [PATCH 10/16] iomap: only call into ->submit_read when there is a read_ctx Christoph Hellwig
2026-02-23 13:20 ` [PATCH 11/16] iomap: allow file systems to hook into buffered read bio submission Christoph Hellwig
2026-02-23 13:20 ` [PATCH 12/16] ntfs3: remove copy and pasted iomap code Christoph Hellwig
2026-02-23 16:27   ` Darrick J. Wong
2026-02-27 13:46   ` Konstantin Komarov
2026-03-03 15:21     ` Christoph Hellwig
2026-03-04  9:57       ` Konstantin Komarov
2026-02-23 13:20 ` [PATCH 13/16] iomap: add a bioset pointer to iomap_read_folio_ops Christoph Hellwig
2026-02-23 13:20 ` [PATCH 14/16] iomap: support ioends for buffered reads Christoph Hellwig
2026-02-23 13:20 ` [PATCH 15/16] iomap: support T10 protection information Christoph Hellwig
2026-02-23 13:20 ` [PATCH 16/16] xfs: " Christoph Hellwig
2026-03-02 10:11 ` support file system generated / verified integrity information v4 Christian Brauner
2026-03-02 13:48   ` Christoph Hellwig
2026-03-04 12:55     ` Christian Brauner
2026-03-09 14:52 ` (subset) " Jens Axboe
2026-03-10 10:16   ` Christian Brauner

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=20260223132021.292832-6-hch@lst.de \
    --to=hch@lst.de \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=nvdimm@lists.linux.dev \
    /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