public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
	Yu Kuai <yukuai3@huawei.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
	linux-raid@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] block: split struct bio_integrity_data
Date: Wed, 19 Feb 2025 17:40:35 +0100	[thread overview]
Message-ID: <cc3ebf94-e1e2-48bc-83f2-d7aaf65b3d27@suse.de> (raw)
In-Reply-To: <20250218182207.3982214-4-hch@lst.de>

On 2/18/25 19:21, Christoph Hellwig wrote:
> Many of the fields in struct bio_integrity_data are only needed for
> the default integrity buffer in the block layer, and the variable
> sized array at the end of the structure makes it very hard to embed
> into caller allocated structures.
> 
> Reduce struct bio_integrity_data to the minimal structure needed in
> common code, and create containing structures for the payload + bvec
> allocation for submitter provided buffers, and the default integrity
> code.  Stop using mempools for the submitter buffers as they don't sit
> below the I/O stack, and instead always use the mempool for automatic
> integrity metadata instead of depending on bio_set that is submitter
> controlled and thus often doesn't have the mempool initialized.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
> ---
>   block/bio-integrity-auto.c          |  75 +++++++++++++------
>   block/bio-integrity.c               | 107 ++++++----------------------
>   block/bio.c                         |   6 --
>   block/blk.h                         |   2 +-
>   block/t10-pi.c                      |   6 +-
>   drivers/md/dm-integrity.c           |  12 ----
>   drivers/md/dm-table.c               |   6 --
>   drivers/md/md.c                     |  13 ----
>   drivers/target/target_core_iblock.c |  12 ----
>   include/linux/bio-integrity.h       |  25 +------
>   include/linux/bio.h                 |   4 --
>   11 files changed, 80 insertions(+), 188 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  parent reply	other threads:[~2025-02-19 16:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 18:21 split out the auto-PI code and data structures Christoph Hellwig
2025-02-18 18:21 ` [PATCH 1/3] block: mark bounce buffering as incompatible with integrity Christoph Hellwig
2025-02-18 18:30   ` Johannes Thumshirn
2025-02-19 16:35   ` Hannes Reinecke
2025-02-21  6:04   ` Anuj gupta
2025-02-18 18:21 ` [PATCH 2/3] block: move the block layer auto-integrity code into a new file Christoph Hellwig
2025-02-18 18:28   ` Johannes Thumshirn
2025-02-19  1:35   ` Martin K. Petersen
2025-02-19 11:33   ` Kanchan Joshi
2025-02-19 16:37   ` Hannes Reinecke
2025-02-21  6:04   ` Anuj gupta
2025-02-18 18:21 ` [PATCH 3/3] block: split struct bio_integrity_data Christoph Hellwig
2025-02-19 11:34   ` Kanchan Joshi
2025-02-19 16:40   ` Hannes Reinecke [this message]
2025-02-21  6:07   ` Anuj gupta
  -- strict thread matches above, loose matches on Subject: below --
2025-01-31 12:24 RFC: split out the auto-PI code and data structures Christoph Hellwig
2025-01-31 12:24 ` [PATCH 3/3] block: split struct bio_integrity_data Christoph Hellwig
2025-02-03 19:45   ` 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=cc3ebf94-e1e2-48bc-83f2-d7aaf65b3d27@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --cc=target-devel@vger.kernel.org \
    --cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox