All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: virtio-comment@lists.linux.dev, virtio-dev@lists.linux.dev,
	david@redhat.com
Subject: Re: [PATCH 0/1] balloon: introduce 6 memory statistics
Date: Mon, 27 May 2024 02:41:14 -0400	[thread overview]
Message-ID: <20240527023734-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240513121005.459013-1-pizhenwei@bytedance.com>

On Mon, May 13, 2024 at 08:10:04PM +0800, zhenwei pi wrote:
> Hi,
> 
> There is a previous discussion about the new memory statistics:
> https://lore.kernel.org/linux-kernel/20240423034109.1552866-1-pizhenwei@bytedance.com/T/

> This may be helpful to describe the usage of these counters.

It's ok to add a link but you really should include the
motivation with the patch, and preferably in the commit log
not the cover letter.


I think the qemu patches actually include a lot of good info
about the statistics collected. But they also raise a lot
of questions that would be of interest to the TC.



> 
> zhenwei pi (1):
>   balloon: introduce 6 memory statistics
> 
>  device-types/balloon/description.tex | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> -- 
> 2.34.1
> 


      parent reply	other threads:[~2024-05-27  6:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 12:10 [PATCH 0/1] balloon: introduce 6 memory statistics zhenwei pi
2024-05-13 12:10 ` [PATCH 1/1] " zhenwei pi
2024-05-21  3:50   ` Michael S. Tsirkin
2024-05-21  4:57     ` zhenwei pi
     [not found]     ` <db3b8a29-db67-4e85-9b2d-314cb2924c88@bytedance.com>
2024-05-27  3:34       ` PING: " zhenwei pi
2024-05-27  6:37   ` Michael S. Tsirkin
2024-05-27  9:02     ` zhenwei pi
2024-05-21  3:43 ` PING: [PATCH 0/1] " zhenwei pi
2024-05-27  6:41 ` 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=20240527023734-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=david@redhat.com \
    --cc=pizhenwei@bytedance.com \
    --cc=virtio-comment@lists.linux.dev \
    --cc=virtio-dev@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.