From: "Michael S. Tsirkin" <mst@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.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: [PATCH 0/3] Improve memory statistics for virtio balloon
Date: Mon, 22 Apr 2024 16:57:56 -0400 [thread overview]
Message-ID: <20240422165725-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240418062602.1291391-1-pizhenwei@bytedance.com>
On Thu, Apr 18, 2024 at 02:25:59PM +0800, zhenwei pi wrote:
> RFC -> v1:
> - several text changes: oom-kill -> oom-kills, SCAN_ASYNC -> ASYN_SCAN.
> - move vm events codes into '#ifdef CONFIG_VM_EVENT_COUNTERS'
>
> RFC version:
> Link: https://lore.kernel.org/lkml/20240415084113.1203428-1-pizhenwei@bytedance.com/T/#m1898963b3c27a989b1123db475135c3ca687ca84
Make sure this builds without introducing new warnings please.
> zhenwei pi (3):
> virtio_balloon: introduce oom-kill invocations
> virtio_balloon: introduce memory allocation stall counter
> virtio_balloon: introduce memory scan/reclaim info
>
> drivers/virtio/virtio_balloon.c | 30 ++++++++++++++++++++++++++++-
> include/uapi/linux/virtio_balloon.h | 16 +++++++++++++--
> 2 files changed, 43 insertions(+), 3 deletions(-)
>
> --
> 2.34.1
prev parent reply other threads:[~2024-04-22 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 6:25 [PATCH 0/3] Improve memory statistics for virtio balloon zhenwei pi
2024-04-18 6:26 ` [PATCH 1/3] virtio_balloon: introduce oom-kill invocations zhenwei pi
2024-04-18 10:58 ` David Hildenbrand
2024-04-18 6:26 ` [PATCH 2/3] virtio_balloon: introduce memory allocation stall counter zhenwei pi
2024-04-18 11:49 ` David Hildenbrand
2024-04-21 3:43 ` kernel test robot
2024-04-18 6:26 ` [PATCH 3/3] virtio_balloon: introduce memory scan/reclaim info zhenwei pi
2024-04-18 11:51 ` David Hildenbrand
2024-04-22 20:57 ` Michael S. Tsirkin [this message]
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=20240422165725-mutt-send-email-mst@kernel.org \
--to=mst@redhat.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=pizhenwei@bytedance.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 read-only IMAP folder(s) and NNTP newsgroup(s).