qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [PATCH] hw/arm: add static NVDIMMs in device tree
Date: Wed, 20 Aug 2025 11:29:12 +0200	[thread overview]
Message-ID: <45c2fe3a-fb71-4cc2-96ff-20612da34627@redhat.com> (raw)
In-Reply-To: <dd4fff02-7c73-412f-bf8c-ee8446cd9b11@linux.alibaba.com>

On 20.08.25 06:10, Gao Xiang wrote:
> (try to Cc David and Paolo for some discussion...)
> 
> Hi David and Paolo,
> 

Hi!

> If possible, could you share some thoughts about this, because
> currently each `memory-backend-file` has their own page cache
> on the host, but if QEMU can provide one nvdimm device backed
> by multiple files, so that EROFS can share memory in finer
> layer granularity on the host.  (we don't need to attach so
> many devices, because some container images can be dozens of
> layers.)

Sounds a bit like what virtio-fs does?

> 
> Without further investigatation, I wonder which direction is
> better:
> 
>     1) one memory-backend-file backed by multiple files;

No.

> 
>     2) nvdimm, virtio-pmem, .. backed by multiple
>        `memory-backend-file`s..

Better.

> 
> Currently I don't have extra slot to look into the QEMU codebase,
> but if the idea is acceptable, I will try to work on this later.

But is this really better than just using many devices?

-- 
Cheers

David / dhildenb



  reply	other threads:[~2025-08-20  9:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 12:21 [PATCH] hw/arm: add static NVDIMMs in device tree Manos Pitsidianakis
2025-07-31  8:38 ` Philippe Mathieu-Daudé
2025-07-31  9:42   ` Manos Pitsidianakis
2025-07-31 10:00 ` Jonathan Cameron via
2025-07-31 11:14   ` Shameerali Kolothum Thodi via
2025-07-31 12:20     ` Manos Pitsidianakis
2025-08-01 11:03       ` Igor Mammedov
2025-08-01 11:35         ` Peter Maydell
2025-08-01  6:58     ` Gao Xiang
2025-08-20  4:10       ` Gao Xiang
2025-08-20  9:29         ` David Hildenbrand [this message]
2025-08-20 10:11           ` Gao Xiang

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=45c2fe3a-fb71-4cc2-96ff-20612da34627@redhat.com \
    --to=david@redhat.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).