[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9653d74f-ffff-6a25-8c99-5565bcab4d5c@virtuozzo.com>
Date: Wed, 10 Aug 2022 08:14:06 +0300
From: Alexander Atanasov <alexander.atanasov@...tuozzo.com>
To: Muchun Song <muchun.song@...ux.dev>
Cc: Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>, kernel@...nvz.org,
David Hildenbrand <david@...hat.com>,
Wei Liu <wei.liu@...nel.org>, Nadav Amit <namit@...are.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v1 1/2] Enable balloon drivers to report inflated memory
Hello,
On 10.08.22 6:05, Muchun Song wrote:
>
>
>> On Aug 9, 2022, at 17:49, Alexander Atanasov <alexander.atanasov@...tuozzo.com> wrote:
>>
>> Display reported in /proc/meminfo as:
>
> Hi,
>
> I am not sure if this is a right place (meminfo) to put this statistic in since
> it is the accounting from a specific driver. IIUC, this driver is only installed
> in a VM, then this accounting will always be zero if this driver is not installed.
> Is this possible to put it in a driver-specific sysfs file (maybe it is better)?
> Just some thoughts from me.
Yes, it is only used if run under hypervisor but it is under a config
option for that reason.
There are several balloon drivers that will use it, not only one driver
- virtio, VMWare, HyperV, XEN and possibly others. I made one as an
example. Initially i worked on a patches for debugfs but discussion lead
to put it into a centralized place.
--
Regards,
Alexander Atanasov
Powered by blists - more mailing lists