From: David Hildenbrand <david@redhat.com>
To: Yangming <yangming73@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "wangzhigang (O)" <wangzhigang17@huawei.com>,
"zhangliang (AG)" <zhangliang5@huawei.com>,
xiqi <xiqi2@huawei.com>
Subject: Re: Reply: [PATCH] virtio-balloon: optimize the virtio-balloon on the ARM platform.
Date: Mon, 27 Feb 2023 10:22:43 +0100 [thread overview]
Message-ID: <336a4051-8f23-f6fa-d481-39c47b8bf5cf@redhat.com> (raw)
In-Reply-To: <6d5f8a599b6a41de8885434e6bb91c9a@huawei.com>
On 27.02.23 02:25, Yangming wrote:
>
>
>> On Fri, Feb 24, 2023 at 08:23:40AM +0000, Yangming wrote:
>>>
>>> Optimize the virtio-balloon feature on the ARM platform by adding a
>> variable to keep track of the current hot-plugged pc-dimm size, instead of
>> traversing the virtual machine's memory modules to count the current RAM
>> size during the balloon inflation or deflation process. This variable can be
>> updated only when plugging or unplugging the device, which will result in an
>> increase of more than 60% efficiency of balloon process on the ARM platform.
>>>
>>> Signed-off-by: Qi Xi <xiqi2@huawei.com>
>>> Signed-off-by: Ming Yang yangming73@huawei.com
>>
>> What kind of performance gains are achieved by this patch?
>> Pls include some measurements: before and after.
>>
>>
>>> ---
>>> hw/mem/pc-dimm.c | 2 ++
>>> hw/virtio/virtio-balloon.c | 44 +++++++++++++-------------------------
>>> include/hw/boards.h | 1 +
>>> 3 files changed, 18 insertions(+), 29 deletions(-)
>>>
>>> diff --git a/hw/mem/pc-dimm.c b/hw/mem/pc-dimm.c index
>> 50ef83215c..192fc7922c 100644
>>> --- a/hw/mem/pc-dimm.c
>>> +++ b/hw/mem/pc-dimm.c
>>> @@ -81,6 +81,7 @@ void pc_dimm_plug(PCDIMMDevice *dimm,
>> MachineState *machine)
>>>
>>> memory_device_plug(MEMORY_DEVICE(dimm), machine);
>>> vmstate_register_ram(vmstate_mr, DEVICE(dimm));
>>> + machine->device_memory->dimm_size += vmstate_mr->size;
>>> }
>>>
>>> void pc_dimm_unplug(PCDIMMDevice *dimm, MachineState *machine)
>> @@ -90,6 +91,7 @@ void pc_dimm_unplug(PCDIMMDevice *dimm,
>> MachineState *machine)
>>>
>>> memory_device_unplug(MEMORY_DEVICE(dimm), machine);
>>> vmstate_unregister_ram(vmstate_mr, DEVICE(dimm));
>>> + machine->device_memory->dimm_size -= vmstate_mr->size;
>>> }
>>>
>>> static int pc_dimm_slot2bitmap(Object *obj, void *opaque) diff --git
>> a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c index
>> 746f07c4d2..40fa40109d 100644
>>> --- a/hw/virtio/virtio-balloon.c
>>> +++ b/hw/virtio/virtio-balloon.c
>>> @@ -729,37 +729,14 @@ static void virtio_balloon_get_config(VirtIODevice
>> *vdev, uint8_t *config_data)
>>> memcpy(config_data, &config, virtio_balloon_config_size(dev)); }
>>>
>>> -static int build_dimm_list(Object *obj, void *opaque) -{
>>> - GSList **list = opaque;
>>> -
>>> - if (object_dynamic_cast(obj, TYPE_PC_DIMM)) {
>>> - DeviceState *dev = DEVICE(obj);
>>> - if (dev->realized) { /* only realized DIMMs matter */
>>> - *list = g_slist_prepend(*list, dev);
>>> - }
>>> - }
>>> -
>>> - object_child_foreach(obj, build_dimm_list, opaque);
>>> - return 0;
>>> -}
>>> -
>>> static ram_addr_t get_current_ram_size(void) {
>>> - GSList *list = NULL, *item;
>>> - ram_addr_t size = current_machine->ram_size;
>>> -
>>> - build_dimm_list(qdev_get_machine(), &list);
>>> - for (item = list; item; item = g_slist_next(item)) {
>>> - Object *obj = OBJECT(item->data);
>>> - if (!strcmp(object_get_typename(obj), TYPE_PC_DIMM)) {
>>> - size += object_property_get_int(obj, PC_DIMM_SIZE_PROP,
>>> - &error_abort);
>>> - }
>>> + MachineState *machine = MACHINE(qdev_get_machine());
>>> + if (machine->device_memory != NULL) {
>>> + return machine->ram_size + machine->device_memory->dimm_size;
>>> + } else {
>>> + return machine->ram_size;
>>> }
>>> - g_slist_free(list);
>>> -
>>> - return size;
>>> }
>>>
>>> static bool virtio_balloon_page_poison_support(void *opaque) @@ -776,7
>> +753,11 @@ static void virtio_balloon_set_config(VirtIODevice *vdev,
>>> VirtIOBalloon *dev = VIRTIO_BALLOON(vdev);
>>> struct virtio_balloon_config config;
>>> uint32_t oldactual = dev->actual;
>>> - ram_addr_t vm_ram_size = get_current_ram_size();
>>> + ram_addr_t vm_ram_size;
>>> + ram_addr_t vm_ram_size_new;
>>> +
>>> +retry:
>>> + vm_ram_size = get_current_ram_size();
>>>
>>> memcpy(&config, config_data, virtio_balloon_config_size(dev));
>>> dev->actual = le32_to_cpu(config.actual); @@ -784,6 +765,11 @@ static
>> void virtio_balloon_set_config(VirtIODevice *vdev,
>>> qapi_event_send_balloon_change(vm_ram_size -
>>> ((ram_addr_t) dev->actual << VIRTIO_BALLOON_PFN_SHIFT));
>>> }
>>> + vm_ram_size_new = get_current_ram_size();
>>> + if (vm_ram_size_new != vm_ram_size) {
>>> + goto retry;
>>> + }
>>> +
>>
>> What is this doing? needs and comment.
>> And please don't implement loops using goto.
>>
>>
>>> dev->poison_val = 0;
>>> if (virtio_balloon_page_poison_support(dev)) {
>>> dev->poison_val = le32_to_cpu(config.poison_val); diff --git
>> a/include/hw/boards.h b/include/hw/boards.h index
>> 6fbbfd56c8..551b4b419e 100644
>>> --- a/include/hw/boards.h
>>> +++ b/include/hw/boards.h
>>> @@ -296,6 +296,7 @@ struct MachineClass { typedef struct
>> DeviceMemoryState {
>>> hwaddr base;
>>> MemoryRegion mr;
>>> + ram_addr_t dimm_size;
>>> } DeviceMemoryState;
>>>
>>> /**
>>> --
>>> 2.33.0
>
>
> Optimize the virtio-balloon feature on the ARM platform by adding
> a variable to keep track of the current hot-plugged pc-dimm size,
> instead of traversing the virtual machine's memory modules to count
> the current RAM size during the balloon inflation or deflation
> process. This variable can be updated only when plugging or unplugging
> the device, which will result in an increase of approximately 60%
> efficiency of balloon process on the ARM platform.
>
> We tested the total amount of time required for the balloon inflation process on ARM:
> inflate the balloon to 64GB of a 128GB guest under stress.
> Before: 102 seconds
> After: 42 seconds
>
> Signed-off-by: Qi Xi <xiqi2@huawei.com>
> Signed-off-by: Ming Yang yangming73@huawei.com
> ---
Acked-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-02-27 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 1:25 Reply: [PATCH] virtio-balloon: optimize the virtio-balloon on the ARM platform Yangming via
2023-02-27 9:22 ` David Hildenbrand [this message]
2023-02-27 15:59 ` 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=336a4051-8f23-f6fa-d481-39c47b8bf5cf@redhat.com \
--to=david@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangzhigang17@huawei.com \
--cc=xiqi2@huawei.com \
--cc=yangming73@huawei.com \
--cc=zhangliang5@huawei.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).