From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org
Cc: martin.petersen@oracle.com
Subject: [PATCHSET 0/3] Integrity cleanups and optimization
Date: Thu, 11 Jan 2024 09:00:18 -0700 [thread overview]
Message-ID: <20240111160226.1936351-1-axboe@kernel.dk> (raw)
Hi,
1 gets rid of the dummy nop profile, 2 marks the queue as having an
actual profile, and 3 avoids calling into bio_integrity_prep() if we
don't have a profile. This both reduces code (getting rid of the nop
profile) and reduces the overhead of the standard setup of having
integrity enabled in kconfig, yet not using a device with an integrity
profile.
block/blk-integrity.c | 38 ++++++++++----------------------------
block/blk-mq.c | 11 +++++++----
include/linux/blkdev.h | 1 +
3 files changed, 18 insertions(+), 32 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-01-11 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 16:00 Jens Axboe [this message]
2024-01-11 16:00 ` [PATCH 1/3] block/integrity: make profile optional Jens Axboe
2024-01-11 16:05 ` Christoph Hellwig
2024-01-11 16:09 ` Keith Busch
2024-01-11 16:19 ` Jens Axboe
2024-01-11 16:00 ` [PATCH 2/3] block/integrity: flag the queue if it has an integrity profile Jens Axboe
2024-01-11 16:06 ` Christoph Hellwig
2024-01-11 16:16 ` Jens Axboe
2024-01-11 16:18 ` Christoph Hellwig
2024-01-11 16:00 ` [PATCH 3/3] block: only call bio_integrity_prep() if necessary Jens Axboe
2024-01-11 16:28 ` Keith Busch
2024-01-11 18:50 ` Jens Axboe
2024-01-11 16:08 ` [PATCHSET 0/3] Integrity cleanups and optimization Christoph Hellwig
2024-01-11 16:24 ` Martin K. Petersen
2024-01-11 16:34 ` Mike Snitzer
2024-01-11 17:07 ` Mike Snitzer
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=20240111160226.1936351-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).