All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Tomáš Golembiovský" <tgolembi@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	virtio-dev@lists.oasis-open.org,
	Jonathan Helman <jonathan.helman@oracle.com>
Subject: Re: [virtio-dev] [PATCH] content: document balloon memory statistics
Date: Tue, 27 Feb 2018 21:56:04 +0200	[thread overview]
Message-ID: <20180227215553-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180221184417.7d5bf2df@fiorina>

On Wed, Feb 21, 2018 at 06:44:17PM +0100, Tomáš Golembiovský wrote:
> On Wed, 21 Feb 2018 11:33:28 +0000
> Stefan Hajnoczi <stefanha@redhat.com> wrote:
> 
> > On Wed, Feb 21, 2018 at 12:11:35AM +0100, Tomáš Golembiovský wrote:
> > > On Tue, 20 Feb 2018 17:15:44 +0000
> > > Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > > 
> > > > On Mon, Feb 19, 2018 at 02:10:29PM +0100, Tomáš Golembiovský wrote:
> > > > > +\item[VIRTIO_BALLOON_S_CACHES (7)] The amount of memory currently used for
> > > > > +  caching files and other data from disk (in bytes).
> > > > >  \end{description}  
> > > > 
> > > > This one is somewhat vague.  I'm not sure if it means guest page cache
> > > > specifically or something more general.
> > > > 
> > > > On the other hand, the numbers tend to be OS specific...
> > > 
> > > We should come up with a definition that is as definite as possible
> > > while leaving room for all systems to substitute a value that is
> > > natively available. So if anyone has a better formulation then please
> > > advise. The original intent was not to create a Linux specific field.
> > > 
> > > On Linux the value corresponds to Buffers + Cached + SwapCached memory
> > > stats. Correct me if I'm wrong but that should be all clean pages that
> > > have a counterpart on disk and can be quickly reclaimed and used for
> > > something else (without additional IO).
> > 
> > Thanks for clarifying.  Based on what you posted, how about:
> > 
> > "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."
> > 
> > ?
> 
> Sounds reasonable, thanks
> 
>     Tomas

OK - will you post v2 then?

> 
> > 
> > > On Windows this roughly corresponds to the standby list. Or maybe
> > > standby list plus something else. I suppose there may be some
> > > alternative on BSD too.
> > > 
> > >     Tomas
> > > 
> > > 
> > > -- 
> > > Tomáš Golembiovský <tgolembi@redhat.com>
> 
> 
> -- 
> Tomáš Golembiovský <tgolembi@redhat.com>

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


  reply	other threads:[~2018-02-27 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 13:10 [virtio-dev] [PATCH] content: document balloon memory statistics Tomáš Golembiovský
2018-02-20 17:15 ` Stefan Hajnoczi
2018-02-20 23:11   ` Tomáš Golembiovský
2018-02-21 11:33     ` Stefan Hajnoczi
2018-02-21 17:44       ` Tomáš Golembiovský
2018-02-27 19:56         ` Michael S. Tsirkin [this message]
2018-02-28  9:35           ` 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=20180227215553-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 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.