public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Dave Chinner <david@fromorbit.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Jens Axboe <axboe@kernel.dk>, Jooyung Han <jooyung@google.com>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	zkabelac@redhat.com, dm-devel@lists.linux.dev,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	io-uring@vger.kernel.org
Subject: Re: [PATCH] the dm-loop target
Date: Thu, 20 Mar 2025 07:22:27 -0700	[thread overview]
Message-ID: <Z9wko1GfrScgv4Ev@infradead.org> (raw)
In-Reply-To: <Z9vGxrPzJ6oswWrS@fedora>

On Thu, Mar 20, 2025 at 03:41:58PM +0800, Ming Lei wrote:
> > That does not match my observations in say nvmet.  But if you have
> > numbers please share them.
> 
> Please see the result I posted:
> 
> https://lore.kernel.org/linux-block/Z9FFTiuMC8WD6qMH@fedora/

That shows it improves numbers and not that it doens't.


  reply	other threads:[~2025-03-20 14:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b3caee06-c798-420e-f39f-f500b3ea68ca@redhat.com>
     [not found] ` <Z8XlvU0o3C5hAAaM@infradead.org>
     [not found]   ` <8adb8df2-0c75-592d-bc3e-5609bb8de8d8@redhat.com>
     [not found]     ` <Z8Zh5T9ZtPOQlDzX@dread.disaster.area>
     [not found]       ` <1fde6ab6-bfba-3dc4-d7fb-67074036deb0@redhat.com>
     [not found]         ` <Z8eURG4AMbhornMf@dread.disaster.area>
     [not found]           ` <81b037c8-8fea-2d4c-0baf-d9aa18835063@redhat.com>
     [not found]             ` <Z8zbYOkwSaOJKD1z@fedora>
     [not found]               ` <a8e5c76a-231f-07d1-a394-847de930f638@redhat.com>
     [not found]                 ` <Z8-ReyFRoTN4G7UU@dread.disaster.area>
2025-03-11 10:43                   ` [PATCH] the dm-loop target Ming Lei
2025-03-12  2:34                     ` Dave Chinner
2025-03-12  6:24                       ` Christoph Hellwig
2025-03-12  8:26                       ` Ming Lei
2025-03-13  1:36                         ` Ming Lei
2025-03-13 16:36                         ` Mikulas Patocka
2025-03-18  4:27                           ` Dave Chinner
2025-03-18  7:57                             ` Christoph Hellwig
2025-03-18  9:34                               ` Ming Lei
2025-03-20  7:08                                 ` Christoph Hellwig
2025-03-20  7:41                                   ` Ming Lei
2025-03-20 14:22                                     ` Christoph Hellwig [this message]
2025-03-20 14:36                                       ` Ming Lei
2025-03-25 10:15                                     ` Dave Chinner
2025-03-25 12:23                                       ` Ming Lei

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=Z9wko1GfrScgv4Ev@infradead.org \
    --to=hch@infradead.org \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=david@fromorbit.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=heinzm@redhat.com \
    --cc=io-uring@vger.kernel.org \
    --cc=jooyung@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@kernel.org \
    --cc=zkabelac@redhat.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