public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Han Zhang <ihanzhzh@gmail.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com, tfanelli@redhat.com
Subject: Re: [GSoC 2026] vhost-user memory isolation proposal feedback request
Date: Tue, 24 Mar 2026 18:26:17 +0100	[thread overview]
Message-ID: <cf2e482e-65fd-418e-bdda-9948c2b39ff3@redhat.com> (raw)
In-Reply-To: <CAHjCdDAJomXwQ8Z0kkiDGn_8hLWredsby3Nwy4rRgeC9sywc8A@mail.gmail.com>

Hi Han,

I’ve taken a look at your proposal, thanks for submitting it!

It clearly shows you looked into the code and the vhost-user spec and 
made yourself familiar with both, that’s very good. I find it a solid 
concept. I also like your clear separation in fundamental work and later 
optimization.

I have one question: In the optimization section, you suggest using a 
memory pool. I fully agree that’s a good optimization, but it makes me 
wonder what model you have in mind for the original implementation. Do 
you plan on allocating a new buffer for each request? (To be clear: I’m 
not saying that would be a bad idea for the initial proof-of-concept, 
I’m just asking for clarification.)

To help make these detail questions clearer, could you lay out how an 
example request from the guest to the vhost-user back-end would go 
through all the layers, and the response back?


Hanna



  parent reply	other threads:[~2026-03-24 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 11:17 [GSoC 2026] vhost-user memory isolation proposal feedback request Han Zhang
2026-03-09 16:40 ` Hanna Czenczek
2026-03-24 17:26 ` Hanna Czenczek [this message]
2026-03-25  2:11   ` Han Zhang
2026-03-25 16:27     ` Hanna Czenczek

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=cf2e482e-65fd-418e-bdda-9948c2b39ff3@redhat.com \
    --to=hreitz@redhat.com \
    --cc=ihanzhzh@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=tfanelli@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