[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e6f2d09-e5cf-7f8d-965d-a39bfb0ea286@redhat.com>
Date: Fri, 14 Oct 2022 15:40:10 +0200
From: David Hildenbrand <david@...hat.com>
To: Alexander Atanasov <alexander.atanasov@...tuozzo.com>,
Nadav Amit <nadav.amit@...il.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>, kernel@...nvz.org,
Linux Virtualization <virtualization@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>
Subject: Re: RFC [PATCH v4 2/7] Enable balloon drivers to report inflated
memory
>>>
>>> Other problem is that there are drivers that do not use
>>> adjust_managed_page_count().
>>
>> Which ones? Do we care?
>
> VMWare and Virtio balloon drivers. I recently proposed to unify them and
> the objection was that it would break existing users - which is valid so
> we must care i guess.
I'm confused, I think we care about actual adjustment of the total pages
available here, that we want to notify the system about. These
approaches (vmware, virtio-balloon with deflate-on-oom) don't adjust
totalpages, because the assumption is that we can get back the inflated
memory any time we really need it automatically.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists