From: Christoph Hellwig <[email protected]>
To: Ming Lei <[email protected]>
Cc: Christoph Hellwig <[email protected]>,
Dave Chinner <[email protected]>,
Mikulas Patocka <[email protected]>,
Jens Axboe <[email protected]>, Jooyung Han <[email protected]>,
Alasdair Kergon <[email protected]>,
Mike Snitzer <[email protected]>,
Heinz Mauelshagen <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: [PATCH] the dm-loop target
Date: Thu, 20 Mar 2025 07:22:27 -0700 [thread overview]
Message-ID: <[email protected]> (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.
next prev parent reply other threads:[~2025-03-20 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
[not found] ` <Z8zbYOkwSaOJKD1z@fedora>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
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
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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