Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Tomáš Golembiovský" <tgolembi@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Jonathan Helman <jonathan.helman@oracle.com>
Subject: [virtio-dev] Re: [PATCH v2] content: document balloon memory statistics
Date: Mon, 5 Mar 2018 16:16:28 +0200	[thread overview]
Message-ID: <20180305161419-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <7849539ddc252748908b3ff62ca6539b6dea73b0.1519303843.git.tgolembi@redhat.com>

On Thu, Feb 22, 2018 at 01:50:52PM +0100, Tomáš Golembiovský wrote:
> Linux kernel provides some balloon memory statistics that were not
> included in the specs. Include them to avoid any ID clashes in the
> future.
> 
> Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>

OK when you feel it's ready, pls open an issue in github,
don't forget to include link to list archives (this email).
Then send an email so I can start the voting.

> ---
>  content.tex | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/content.tex b/content.tex
> index c7ef7fd..7e9e026 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -5028,6 +5028,8 @@ struct virtio_balloon_stat {
>  #define VIRTIO_BALLOON_S_MINFLT   3
>  #define VIRTIO_BALLOON_S_MEMFREE  4
>  #define VIRTIO_BALLOON_S_MEMTOT   5
> +#define VIRTIO_BALLOON_S_AVAIL    6
> +#define VIRTIO_BALLOON_S_CACHES   7
>          le16 tag;
>          le64 val;
>  } __attribute__((packed));
> @@ -5109,6 +5111,13 @@ first buffer.
>  
>  \item[VIRTIO_BALLOON_S_MEMTOT (5)] The total amount of memory available
>    (in bytes).
> +
> +\item[VIRTIO_BALLOON_S_AVAIL (6)] An estimate of how much memory is available
> +  (in bytes) for starting new applications, without pushing the system to swap.
> +
> +\item[VIRTIO_BALLOON_S_CACHES (7)] The amount of memory, in bytes, that can be
> +  quickly reclaimed without additional I/O. Typically these pages are used for
> +  caching files from disk.
>  \end{description}
>  
>  \section{SCSI Host Device}\label{sec:Device Types / SCSI Host Device}
> -- 
> 2.16.1

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2018-03-05 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 12:50 [virtio-dev] [PATCH v2] content: document balloon memory statistics Tomáš Golembiovský
2018-03-05 14:08 ` Stefan Hajnoczi
2018-03-05 14:16 ` Michael S. Tsirkin [this message]
2018-03-09 22:53 ` [virtio-dev] " Michael S. Tsirkin
2018-03-11 19:19   ` Tomáš Golembiovský

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=20180305161419-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jonathan.helman@oracle.com \
    --cc=stefanha@redhat.com \
    --cc=tgolembi@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    /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