From: Romain Francoise <romain@orebokech.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost-net: fall back to vmalloc if high-order allocation fails
Date: Fri, 28 Jun 2013 09:16:59 +0200 [thread overview]
Message-ID: <87k3leemc4.fsf@kima.orebokech.com> (raw)
In-Reply-To: <20130123210411.GA9055@redhat.com> (Michael S. Tsirkin's message of "Wed, 23 Jan 2013 23:04:11 +0200")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Wed, Jan 23, 2013 at 09:46:47PM +0100, Romain Francoise wrote:
>> Creating a vhost-net device allocates an object large enough (34320 bytes
>> on x86-64) to trigger an order-4 allocation, which may fail if memory if
>> fragmented:
>>
>> libvirtd: page allocation failure: order:4, mode:0x2000d0
>> ...
>> SLAB: Unable to allocate memory on node 0 (gfp=0xd0)
>> cache: size-65536, object size: 65536, order: 4
>> node 0: slabs: 8/8, objs: 8/8, free: 0
>>
>> In that situation, rather than forcing the caller to use regular
>> virtio-net, try to allocate the descriptor with vmalloc().
>>
>> Signed-off-by: Romain Francoise <romain@orebokech.com>
> Thanks for the patch.
> Hmm, I haven't seen this.
> Maybe we should try and reduce our memory usage,
> I will look into this.
Did you get a chance to investigate this? I'm still getting the same
allocation failures with v3.10-rc7 after reverting my local patch.
Thanks.
next prev parent reply other threads:[~2013-06-28 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:46 [PATCH] vhost-net: fall back to vmalloc if high-order allocation fails Romain Francoise
2013-01-23 21:04 ` Michael S. Tsirkin
2013-01-28 3:11 ` David Miller
2013-01-28 9:23 ` Romain Francoise
2013-06-28 7:16 ` Romain Francoise [this message]
2013-01-24 9:45 ` David Laight
2013-01-24 10:06 ` Michael S. Tsirkin
2013-01-24 10:37 ` David Laight
[not found] ` <kdsslg$ddn$1@ger.gmane.org>
2013-01-25 5:15 ` Jason Wang
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=87k3leemc4.fsf@kima.orebokech.com \
--to=romain@orebokech.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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