From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Amit Shah <amit.shah@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] set VIRTIO_BALLOON_F_MUST_TELL_HOST unconditionally
Date: Mon, 18 Apr 2011 08:37:14 -0700 [thread overview]
Message-ID: <1303141034.9615.2651.camel@nimitz> (raw)
In-Reply-To: <4DA89A64.7040809@codemonkey.ws>
On Fri, 2011-04-15 at 14:20 -0500, Anthony Liguori wrote:
> On 04/15/2011 02:15 PM, Dave Hansen wrote:
> > On Fri, 2011-04-15 at 12:17 -0500, Anthony Liguori wrote:
> >> If you're in OOM and you need memory, you can't ask the host for more
> >> and wait for a response. You have to reclaim it immediately.
> > Why not? The call in to the notifier chain the s390 case is
> > synchronous. The OOM only affects one task at a time and won't proceed
> > elsewhere while this is going on.
>
> Because if we tell the host, we have to wait for the host to ack which
> means we'd sleep waiting for an interrupt. Can you do this in the OOM path?
Sure. One of the s390 handlers sleeps today.
> > Why do we even _tell_ qemu, though? The MADV_WILLNEED is nice, but far
> > from being necessary. We could just skip the entire notification in OOM
> > situations.
>
> There's really no particular reason to other than symmetry.
When we get there, it sounds like we can simply _skip_ the notification
in the qemu case.
-- Dave
prev parent reply other threads:[~2011-04-18 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 14:44 [Qemu-devel] [PATCH] set VIRTIO_BALLOON_F_MUST_TELL_HOST unconditionally Dave Hansen
2011-04-15 16:21 ` Anthony Liguori
2011-04-15 16:36 ` Dave Hansen
2011-04-15 17:17 ` Anthony Liguori
2011-04-15 19:15 ` Dave Hansen
2011-04-15 19:20 ` Anthony Liguori
2011-04-18 15:37 ` Dave Hansen [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=1303141034.9615.2651.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).