From: David Hildenbrand <david@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
David Hildenbrand <dhildenb@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 0/3] Hyper-V Dynamic Memory Protocol driver (hv-balloon)
Date: Mon, 21 Sep 2020 11:29:48 +0200 [thread overview]
Message-ID: <e679e7fe-7ca0-c5e4-d024-dc55ed1dd589@redhat.com> (raw)
In-Reply-To: <20200921110023.10f6d01c@redhat.com>
On 21.09.20 11:00, Igor Mammedov wrote:
> On Sun, 20 Sep 2020 15:25:19 +0200
> "Maciej S. Szmigiero" <mail@maciej.szmigiero.name> wrote:
>
>> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>
> From description it sounds like an alternative of virtio-mem,
> CCing David.
Hah! Was already replying when your cc came in (thanks anyway!).
Not quite an alternative to virtio-mem, more like a (in some factors)
optimized alternative to DIMM-based memory hotplug + virtio-balloon.
The core design of virtio-mem avoids basic issues related to memory
ballooning. (it was the result of analyzing existing technologies and
their shortcomings - including HV dynamic memory).
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-09-21 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 13:25 [PATCH 0/3] Hyper-V Dynamic Memory Protocol driver (hv-balloon) Maciej S. Szmigiero
2020-09-20 13:25 ` [PATCH 1/3] haprot: add a device for memory hot-add protocols Maciej S. Szmigiero
2020-09-20 13:25 ` [PATCH 2/3] Add Hyper-V Dynamic Memory Protocol definitions Maciej S. Szmigiero
2020-09-20 13:25 ` [PATCH 3/3] Add a Hyper-V Dynamic Memory Protocol driver (hv-balloon) Maciej S. Szmigiero
2020-09-20 14:16 ` [PATCH 0/3] " no-reply
2020-09-21 9:00 ` Igor Mammedov
2020-09-21 9:29 ` David Hildenbrand [this message]
2020-09-21 9:10 ` David Hildenbrand
2020-09-21 22:22 ` Maciej S. Szmigiero
2020-09-22 7:26 ` David Hildenbrand
2020-09-22 23:19 ` Maciej S. Szmigiero
2020-09-23 12:48 ` David Hildenbrand
2020-09-24 22:37 ` Maciej S. Szmigiero
2020-09-25 6:49 ` David Hildenbrand
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=e679e7fe-7ca0-c5e4-d024-dc55ed1dd589@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dhildenb@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mail@maciej.szmigiero.name \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=vkuznets@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).