public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], [email protected],
	 [email protected], Keith Busch <[email protected]>
Cc: [email protected], [email protected], [email protected],
	 [email protected], Keith Busch <[email protected]>
Subject: Re: [PATCHv5 0/4] block integrity: directly map user space addresses
Date: Thu, 30 Nov 2023 16:09:25 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Thu, 30 Nov 2023 13:53:05 -0800, Keith Busch wrote:
> Handling passthrough metadata ("integrity") today introduces overhead
> and complications that we can avoid if we just map user space addresses
> directly. This patch series implements that, falling back to a kernel
> bounce buffer if necessary.
> 
> v4->v5:
> 
> [...]

Applied, thanks!

[1/4] block: bio-integrity: directly map user buffers
      commit: 5a0584b2c714a219296d97d9f4307ffe53c18937
[2/4] nvme: use bio_integrity_map_user
      commit: aec0ff70f016fdf7b4ba52e34d682a185dd8dd74
[3/4] iouring: remove IORING_URING_CMD_POLLED
      commit: f8243a30dc179ac197bd8315bdf9d55d3d7792c3
[4/4] io_uring: remove uring_cmd cookie
      commit: fb62c0c9b04265539851734ae35cf3f10651a8dd

Best regards,
-- 
Jens Axboe




  parent reply	other threads:[~2023-11-30 23:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231130215715epcas5p33208ca14e69a68402c04e5c743135e6c@epcas5p3.samsung.com>
2023-11-30 21:53 ` [PATCHv5 0/4] block integrity: directly map user space addresses Keith Busch
2023-11-30 21:53   ` [PATCHv5 1/4] block: bio-integrity: directly map user buffers Keith Busch
2023-11-30 21:53   ` [PATCHv5 2/4] nvme: use bio_integrity_map_user Keith Busch
2023-11-30 21:53   ` [PATCHv5 3/4] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-11-30 21:53   ` [PATCHv5 4/4] io_uring: remove uring_cmd cookie Keith Busch
2023-11-30 23:09   ` Jens Axboe [this message]
2023-12-01 10:43   ` [PATCHv5 0/4] block integrity: directly map user space addresses Kanchan Joshi
2023-12-01 18:42     ` Keith Busch
2023-12-01 22:49       ` Keith Busch
2023-12-02  1:31         ` Jens Axboe
2023-12-02  2:04           ` Kanchan Joshi
2023-12-02 14:58             ` Jens Axboe

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=170138576512.699292.6762410631511683338.b4-ty@kernel.dk \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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