From: David Hildenbrand <david@redhat.com>
To: Alexander Atanasov <alexander.atanasov@virtuozzo.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>
Cc: kernel@openvz.org, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] Create debugfs file with virtio balloon usage information
Date: Thu, 14 Jul 2022 15:24:40 +0200 [thread overview]
Message-ID: <bfb7ab7f-6c17-e1fe-d87e-b19312f06e0c@redhat.com> (raw)
In-Reply-To: <123b7518-b0c9-171c-9596-73654691ee58@virtuozzo.com>
On 14.07.22 15:20, Alexander Atanasov wrote:
> Hello,
>
> On 14/07/2022 14:35, David Hildenbrand wrote:
>> On 05.07.22 10:36, Alexander Atanasov wrote:
>>> Allow the guest to know how much it is ballooned by the host.
>>> It is useful when debugging out of memory conditions.
>>>
>>> When host gets back memory from the guest it is accounted
>>> as used memory in the guest but the guest have no way to know
>>> how much it is actually ballooned.
>>>
>>> Signed-off-by: Alexander Atanasov <alexander.atanasov@virtuozzo.com>
>>> ---
>>> drivers/virtio/virtio_balloon.c | 77 +++++++++++++++++++++++++++++
>>> include/uapi/linux/virtio_balloon.h | 1 +
>>> 2 files changed, 78 insertions(+)
>>>
>>> V2:
>>> - fixed coding style
>>> - removed pretty print
>>> V3:
>>> - removed dublicate of features
>>> - comment about balooned_pages more clear
>>> - convert host pages to balloon pages
>>> V4:
>>> - added a define for BALLOON_PAGE_SIZE to make things clear
>>>
>>> diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
>>> index b9737da6c4dd..dc4ad584b947 100644
>>> --- a/drivers/virtio/virtio_balloon.c
>>> +++ b/drivers/virtio/virtio_balloon.c
>>> @@ -10,6 +10,7 @@
>>> #include <linux/virtio_balloon.h>
>>> #include <linux/swap.h>
>>> #include <linux/workqueue.h>
>>> +#include <linux/debugfs.h>
>>> #include <linux/delay.h>
>>> #include <linux/slab.h>
>>> #include <linux/module.h>
>>> @@ -731,6 +732,77 @@ static void report_free_page_func(struct work_struct *work)
>>> }
>>> }
>>>
>>> +/*
>>> + * DEBUGFS Interface
>>> + */
>>> +#ifdef CONFIG_DEBUG_FS
>>> +
>>> +#define guest_to_balloon_pages(i) ((i)*VIRTIO_BALLOON_PAGES_PER_PAGE)
>>> +/**
>>> + * virtio_balloon_debug_show - shows statistics of balloon operations.
>>> + * @f: pointer to the &struct seq_file.
>>> + * @offset: ignored.
>>> + *
>>> + * Provides the statistics that can be accessed in virtio-balloon in the debugfs.
>>> + *
>>> + * Return: zero on success or an error code.
>>> + */
>>> +
>>> +static int virtio_balloon_debug_show(struct seq_file *f, void *offset)
>>> +{
>>> + struct virtio_balloon *b = f->private;
>>> + u32 num_pages;
>>> + struct sysinfo i;
>>> +
>>> + si_meminfo(&i);
>>> +
>>> + seq_printf(f, "%-22s: %d\n", "page_size", VIRTIO_BALLOON_PAGE_SIZE);
>>> +
>>> + virtio_cread_le(b->vdev, struct virtio_balloon_config, actual,
>>> + &num_pages);
>>> + /*
>>> + * Pages allocated by host from the guest memory.
>>> + * Host inflates the balloon to get more memory.
>>> + * Guest needs to deflate the balloon to get more memory.
>>> + */
>> Please drop that comment. This is basic virtio-balloon operation that
>> must not be explained at this point.
>
> Ok
>
>>> + seq_printf(f, "%-22s: %u\n", "ballooned_pages", num_pages);
>>> +
>>> + /* Total Memory for the guest from host */
>>> + seq_printf(f, "%-22s: %lu\n", "total_pages",
>>> + guest_to_balloon_pages(i.totalram));
>> totalram is calculated from totalram_pages().
>>
>> When we inflate/deflate, we adjust totalram as well via
>> adjust_managed_page_count().
>
> That is true only when not using DEFLATE_ON_OOM.
>
> Otherwise inflated memory is accounted as used and total ram stays the same.
>> Consequently, this doesn't calculate what you actually want?
>> Total memory would be totalram+inflated, current would be totalram.
>
> My calculations are correct for the case deflate_on_oom is enabled.
>
Which is the corner cases. You'd have to special case on DEFLATE_ON_OOM
availability.
>> But, TBH, only export num_pages. User space can just lookup the other
>> information (totalram) via /proc/meminfo.
>
> I have missed that the memory accounting is made differently depending
> on a flag.
>
> Since the calculations are different i'd prefer to have the values
> calculate and printed there.
What about an indication instead, whether or not inflated pages are
accounted into total or not? That would be slightly cleaner IMHO.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-07-14 13:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 8:36 [PATCH v4 1/1] Create debugfs file with virtio balloon usage information Alexander Atanasov
2022-07-05 8:59 ` Michael S. Tsirkin
2022-07-05 9:01 ` Alexander Atanasov
2022-08-09 10:35 ` Michael S. Tsirkin
2022-08-09 13:33 ` Alexander Atanasov
2022-07-13 16:25 ` Alexander Atanasov
2022-07-14 11:35 ` David Hildenbrand
2022-07-14 13:20 ` Alexander Atanasov
2022-07-14 13:24 ` David Hildenbrand [this message]
2022-07-14 13:35 ` Alexander Atanasov
2022-07-14 13:20 ` [PATCH v5 " Alexander Atanasov
2022-07-18 11:35 ` David Hildenbrand
2022-07-25 11:27 ` Alexander Atanasov
2022-07-25 11:36 ` David Hildenbrand
2022-07-26 14:08 ` [PATCH v6 1/2] " Alexander Atanasov
2022-07-26 14:10 ` [PATCH v6 2/2] Unify how inflated memory is accounted in virtio balloon driver Alexander Atanasov
2022-08-01 15:13 ` David Hildenbrand
2022-08-09 10:42 ` Michael S. Tsirkin
2022-08-01 15:18 ` [PATCH v6 1/2] Create debugfs file with virtio balloon usage information David Hildenbrand
2022-08-01 16:34 ` Alexander Atanasov
2022-08-01 20:12 ` David Hildenbrand
2022-08-02 8:53 ` [RFC] how the ballooned memory should be accounted by the drivers inside the guests? (was:[PATCH v6 1/2] Create debugfs file with virtio balloon usage information) Alexander Atanasov
2022-08-02 13:48 ` David Hildenbrand
2022-08-09 9:36 ` Alexander Atanasov
2022-08-09 9:49 ` [PATCH v1 1/2] Enable balloon drivers to report inflated memory Alexander Atanasov
2022-08-09 9:53 ` [PATCH v1 2/2] Drivers: virtio: balloon: Report " Alexander Atanasov
2022-08-09 17:44 ` Nadav Amit
2022-08-15 12:52 ` Alexander Atanasov
2022-08-15 16:05 ` Nadav Amit
2022-08-16 7:50 ` Alexander Atanasov
2022-08-09 10:32 ` [PATCH v1 1/2] Enable balloon drivers to report " Michael S. Tsirkin
2022-08-10 5:54 ` Alexander Atanasov
2022-08-10 6:05 ` Michael S. Tsirkin
2022-08-10 7:50 ` Alexander Atanasov
2022-08-10 9:16 ` Michael S. Tsirkin
2022-08-10 3:05 ` Muchun Song
2022-08-10 5:14 ` Alexander Atanasov
2022-08-09 10:03 ` [RFC] how the ballooned memory should be accounted by the drivers inside the guests? (was:[PATCH v6 1/2] Create debugfs file with virtio balloon usage information) David Hildenbrand
2022-08-09 10:44 ` [PATCH v6 1/2] Create debugfs file with virtio balloon usage information Michael S. Tsirkin
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=bfb7ab7f-6c17-e1fe-d87e-b19312f06e0c@redhat.com \
--to=david@redhat.com \
--cc=alexander.atanasov@virtuozzo.com \
--cc=jasowang@redhat.com \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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