[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <edba66e3-89bd-e7b2-6ebb-3f868c9aec67@virtuozzo.com>
Date: Wed, 19 Oct 2022 14:06:14 +0300
From: Alexander Atanasov <alexander.atanasov@...tuozzo.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Nadav Amit <namit@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Arnd Bergmann <arnd@...db.de>, kernel@...nvz.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v5 6/8] drivers: vmware: balloon - report inflated
memory
On 19.10.22 13:49, Greg Kroah-Hartman wrote:
> On Wed, Oct 19, 2022 at 01:38:13PM +0300, Alexander Atanasov wrote:
>> On 19.10.22 13:26, Greg Kroah-Hartman wrote:
>>> On Wed, Oct 19, 2022 at 12:56:18PM +0300, Alexander Atanasov wrote:
>>>> Update the inflated memory in the mm core on change.
>>>
>>> That says what this does, but not why it is needed.
>>>
>>> Please expand on this.
>>>
>>> Also, is this actually fixing a bug? Is it a new feature? Something
>>> else?
>>
>> The whole series is about adding a new feature - providing access to the
>> balloon inflated memory amount - it's in the cover letter. Should I repeat
>> it for every driver that implements it?
>
> Each commit needs to justify why it is needed on its own. You do not
> provide the needed information here at all to be able to review and
> understand if this commit is even correct or needed.
Ok, understood. I will keep that in mind. Thanks.
--
Regards,
Alexander Atanasov
Powered by blists - more mailing lists