From: Rusty Russell <rusty@rustcorp.com.au>
To: Avi Kivity <avi@redhat.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Minchan Kim <minchan.kim@gmail.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Wu Fengguang <fengguang.wu@intel.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: Page allocation failures in guest
Date: Wed, 12 Aug 2009 12:49:51 +0930 [thread overview]
Message-ID: <200908121249.51973.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A811545.5090209@redhat.com>
On Tue, 11 Aug 2009 04:22:53 pm Avi Kivity wrote:
> On 08/11/2009 09:32 AM, Pierre Ossman wrote:
> > On Mon, 13 Jul 2009 23:59:52 +0900
> > Minchan Kim<minchan.kim@gmail.com> wrote:
> > Any ideas here? Is the virtio net driver very GFP_ATOMIC happy so it
> > drains all those pages? And why is this triggered by a kernel upgrade
> > in the host?
> >
> > Avi?
>
> Rusty?
It's kind of the nature of networking devices :(
I'd say your host now offers GSO features, so the guest allocates big
packets.
> > I doesn't get out of it though, or at least the virtio net driver
> > wedges itself.
There's a fixme to retry when this happens, but this is the first report
I've received. I'll check it out.
Thanks,
Rusty.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-12 3:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 9:51 Page allocation failures in guest Pierre Ossman
2009-07-13 14:59 ` Minchan Kim
2009-08-11 6:32 ` Pierre Ossman
2009-08-11 6:52 ` Avi Kivity
2009-08-12 3:19 ` Rusty Russell [this message]
2009-08-12 5:31 ` Rusty Russell
2009-08-12 5:41 ` Avi Kivity
2009-08-12 6:56 ` Rusty Russell
2009-08-13 20:25 ` Pierre Ossman
2009-08-26 2:17 ` Rusty Russell
2009-08-26 4:55 ` Pierre Ossman
2009-08-26 12:18 ` Rusty Russell
2009-08-26 19:22 ` David Miller
2009-08-12 6:19 ` Pierre Ossman
2009-08-12 7:43 ` Avi Kivity
2009-08-12 8:22 ` Pierre Ossman
2009-08-12 8:35 ` Avi Kivity
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=200908121249.51973.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=avi@redhat.com \
--cc=drzeus-list@drzeus.cx \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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).