From: "hch@lst.de" <hch@lst.de>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "hch@lst.de" <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Chaitanya Kulkarni <ckulkarnilinux@gmail.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH 0/1] nvmet: add basic in-memory backend support
Date: Thu, 6 Nov 2025 12:50:48 +0100 [thread overview]
Message-ID: <20251106115048.GA1916@lst.de> (raw)
In-Reply-To: <dd3a31e0-a170-4d52-8e11-c7229b955a76@nvidia.com>
On Thu, Nov 06, 2025 at 01:20:41AM +0000, Chaitanya Kulkarni wrote:
> Hi Hannes and Christoph,
>
>
> On 11/5/25 05:14, hch@lst.de wrote:
> > But what is the use that requires removing all that overhead / indirection?
> >
> > I think you need to describe that very clearly to make a case. And
> > maybe drop a lot of the marketing sounding overly dramatatic language
> > that really does not help the case.
>
> the quantitative data that proves removing all overhead/indirection
> gives better performance for nvmet-mem-backend against null_blk
> membacked and brd. Here is the link for the comparative data :-
But what is the use case? Why do you care about performance of a
non-persistent DRAM-bound backend?
next prev parent reply other threads:[~2025-11-06 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 8:06 [PATCH 0/1] nvmet: add basic in-memory backend support Chaitanya Kulkarni
2025-11-04 8:06 ` [PATCH 1/1] " Chaitanya Kulkarni
2025-11-04 10:36 ` [PATCH 0/1] " Hannes Reinecke
2025-11-05 0:09 ` Chaitanya Kulkarni
2025-11-05 13:14 ` hch
2025-11-06 1:02 ` Chaitanya Kulkarni
2025-11-06 1:03 ` Chaitanya Kulkarni
2025-11-06 1:20 ` Chaitanya Kulkarni
2025-11-06 11:50 ` hch [this message]
2025-11-10 3:59 ` Chaitanya Kulkarni
2025-11-06 2:54 ` Keith Busch
2025-11-06 2:58 ` Chaitanya Kulkarni
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=20251106115048.GA1916@lst.de \
--to=hch@lst.de \
--cc=chaitanyak@nvidia.com \
--cc=ckulkarnilinux@gmail.com \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).