virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: zhenwei pi <pizhenwei@bytedance.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	virtualization@lists.linux.dev, david@redhat.com,
	jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
	akpm@linux-foundation.org
Subject: Re: Re: [PATCH v3 2/4] virtio_balloon: introduce oom-kill invocations
Date: Tue, 23 Apr 2024 17:21:48 +0800	[thread overview]
Message-ID: <6e9d6af5-74bc-4e97-84c0-2ba8a6499da9@bytedance.com> (raw)
In-Reply-To: <20240423051151-mutt-send-email-mst@kernel.org>



On 4/23/24 17:13, Michael S. Tsirkin wrote:
> On Tue, Apr 23, 2024 at 11:41:07AM +0800, zhenwei pi wrote:

[snip]
>>   #define VIRTIO_BALLOON_S_NAMES_WITH_PREFIX(VIRTIO_BALLOON_S_NAMES_prefix) { \
>>   	VIRTIO_BALLOON_S_NAMES_prefix "swap-in", \
> 
> Looks like a useful extension. But
> any UAPI extension has to go to virtio spec first.
> 

Sure, I'll send related virtio spec changes once virtio comment mail 
list gets ready.

>> @@ -83,7 +84,8 @@ struct virtio_balloon_config {
>>   	VIRTIO_BALLOON_S_NAMES_prefix "available-memory", \
>>   	VIRTIO_BALLOON_S_NAMES_prefix "disk-caches", \
>>   	VIRTIO_BALLOON_S_NAMES_prefix "hugetlb-allocations", \
>> -	VIRTIO_BALLOON_S_NAMES_prefix "hugetlb-failures" \
>> +	VIRTIO_BALLOON_S_NAMES_prefix "hugetlb-failures", \
>> +	VIRTIO_BALLOON_S_NAMES_prefix "oom-kills" \
>>   }
>>   
>>   #define VIRTIO_BALLOON_S_NAMES VIRTIO_BALLOON_S_NAMES_WITH_PREFIX("")
>> -- 
>> 2.34.1
> 

-- 
zhenwei pi

  reply	other threads:[~2024-04-23  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  3:41 [PATCH v3 0/4] Improve memory statistics for virtio balloon zhenwei pi
2024-04-23  3:41 ` [PATCH v3 1/4] virtio_balloon: separate vm events into a function zhenwei pi
2024-04-23 10:03   ` David Hildenbrand
2024-04-23  3:41 ` [PATCH v3 2/4] virtio_balloon: introduce oom-kill invocations zhenwei pi
2024-04-23  9:13   ` Michael S. Tsirkin
2024-04-23  9:21     ` zhenwei pi [this message]
2024-04-23  3:41 ` [PATCH v3 3/4] virtio_balloon: introduce memory allocation stall counter zhenwei pi
2024-04-23  3:41 ` [PATCH v3 4/4] virtio_balloon: introduce memory scan/reclaim info zhenwei pi

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=6e9d6af5-74bc-4e97-84c0-2ba8a6499da9@bytedance.com \
    --to=pizhenwei@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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).