From: "Michael S. Tsirkin" <mst@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org,
Raushaniya Maksudova <rmaksudova@parallels.com>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom
Date: Wed, 1 Apr 2015 12:18:03 +0200 [thread overview]
Message-ID: <20150401121225-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1427881902.3559.34.camel@HansenPartnership.com>
On Wed, Apr 01, 2015 at 12:51:42PM +0300, James Bottomley wrote:
> On Wed, 2015-04-01 at 11:50 +0200, Michael S. Tsirkin wrote:
> > On Wed, Apr 01, 2015 at 12:44:28PM +0300, James Bottomley wrote:
> > > On Fri, 2015-02-27 at 09:57 +0300, Denis V. Lunev wrote:
> > > > Excessive virtio_balloon inflation can cause invocation of OOM-killer,
> > > > when Linux is under severe memory pressure. Various mechanisms are
> > > > responsible for correct virtio_balloon memory management. Nevertheless it
> > > > is often the case that these control tools does not have enough time to
> > > > react on fast changing memory load. As a result OS runs out of memory and
> > > > invokes OOM-killer. The balancing of memory by use of the virtio balloon
> > > > should not cause the termination of processes while there are pages in the
> > > > balloon. Now there is no way for virtio balloon driver to free memory at
> > > > the last moment before some process get killed by OOM-killer.
> > > >
> > > > This does not provide a security breach as balloon itself is running
> > > > inside Guest OS and is working in the cooperation with the host. Thus
> > > > some improvements from Guest side should be considered as normal.
> > > >
> > > > To solve the problem, introduce a virtio_balloon callback which is
> > > > expected to be called from the oom notifier call chain in out_of_memory()
> > > > function. If virtio balloon could release some memory, it will make the
> > > > system return and retry the allocation that forced the out of memory
> > > > killer to run.
> > > >
> > > > This behavior should be enabled if and only if appropriate feature bit
> > > > is set on the device. It is off by default.
> > > >
> > > > This functionality was recently merged into vanilla Linux.
> > > >
> > > > commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
> > > > Author: Raushaniya Maksudova <rmaksudova@parallels.com>
> > > > Date: Mon Nov 10 09:36:29 2014 +1030
> > > >
> > > > This patch adds respective control bits into QEMU. It introduces
> > > > deflate-on-oom option for balloon device which does the trick.
> > >
> > > What's the status on this, please? It's been over a month since this
> > > was posted with no further review feedback, so I think it's ready.
> > > Getting this into qemu is blocking our next step which would be adding
> > > the feature bit to the virtio spec.
> > >
> > > James
> >
> > This was posted after soft feature freeze for 2.3, so it'll have to go
> > into 2.4. I don't see why would this block your work on the spec: you
> > should make progress on this meanwhile.
>
> I can do that ... I just thought the spec was trailing edge, so I was
> waiting to have the patch accepted, which confirms the implementation.
> I didn't want to write it into the spec and have the actual
> implementation changed by review later.
>
> James
>
It's up to you really, I would just like to point out two things:
- spec process is a long one, assuming we accept a spec change,
we go though a public review period, multiple votes etc.
About half a year to release a spec revision with
new features.
So time enough to make minor changes.
- oasis process works like this (roughly):
spec is written
spec goes through a public review process
community standard is published
3 implementations are reported
spec becomes an oasis standard
so implementations aren't required at early stages
--
MST
next prev parent reply other threads:[~2015-04-01 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 6:57 [Qemu-devel] [PATCH v5 0/2] balloon: add a feature bit to let Guest OS deflate Denis V. Lunev
2015-02-27 6:57 ` [Qemu-devel] [PATCH 1/2] balloon: call qdev_alias_all_properties for proxy dev in balloon class init Denis V. Lunev
2015-02-27 6:57 ` [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom Denis V. Lunev
2015-04-01 9:44 ` James Bottomley
2015-04-01 9:50 ` Michael S. Tsirkin
2015-04-01 9:51 ` James Bottomley
2015-04-01 10:18 ` Michael S. Tsirkin [this message]
2015-05-04 9:47 ` Denis V. Lunev
2015-06-08 14:54 ` James Bottomley
2015-06-08 15:24 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2015-02-26 17:39 [Qemu-devel] [PATCH v4 0/2] balloon: add a feature bit to let Guest OS deflate Denis V. Lunev
2015-02-26 17:39 ` [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom Denis V. Lunev
2015-02-26 20:39 ` Eric Blake
2014-11-27 12:44 [Qemu-devel] [PATCH v3 0/2] balloon: add a feature bit to let Guest OS deflate virtio_balloon on OOM Denis V. Lunev
2014-11-27 12:44 ` [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom Denis V. Lunev
2014-11-27 11:45 [Qemu-devel] [PATCH v2 0/2] balloon: add a feature bit to let Guest OS deflate virtio_balloon on OOM Denis V. Lunev
2014-11-27 11:45 ` [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom Denis V. Lunev
2014-11-27 11:50 ` Andrey Korolyov
2014-11-27 12:26 ` Denis V. Lunev
2014-11-27 12:28 ` Michael S. Tsirkin
2014-11-27 14:00 ` Andrey Korolyov
2014-11-27 21:49 ` Michael S. Tsirkin
2014-11-27 22:13 ` Andrey Korolyov
2014-11-27 12:31 ` Michael S. Tsirkin
2014-11-27 12:34 ` Denis V. Lunev
2014-11-26 10:11 [Qemu-devel] [PATCH 0/2] balloon: add a feature bit to let Guest OS deflate virtio_balloon on OOM Denis V. Lunev
2014-11-26 10:11 ` [Qemu-devel] [PATCH 2/2] balloon: add a feature bit to let Guest OS deflate balloon on oom Denis V. Lunev
2014-11-26 11:16 ` Michael S. Tsirkin
2014-11-27 11:04 ` Denis V. Lunev
2014-11-27 11:08 ` Michael S. Tsirkin
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=20150401121225-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aliguori@amazon.com \
--cc=den@openvz.org \
--cc=qemu-devel@nongnu.org \
--cc=rmaksudova@parallels.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).