[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALYGNiOrNfxbCJggraxgiFOdvn3jki_751cpssi+p_eST0Wdgg@mail.gmail.com>
Date: Tue, 28 Oct 2014 23:56:15 +0400
From: Konstantin Khlebnikov <koct9i@...il.com>
To: Konstantin Khlebnikov <koct9i@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Konstantin Khlebnikov <k.khlebnikov@...sung.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Rafael Aquini <aquini@...hat.com>,
Stable <stable@...r.kernel.org>,
Sasha Levin <sasha.levin@...cle.com>
Subject: Re: [PATCH v3 1/4] mm/balloon_compaction: redesign ballooned pages management
On Tue, Oct 28, 2014 at 9:47 PM, Matt Mullins <mmullins@...x.us> wrote:
> On Sat, Sep 27, 2014 at 11:15:16PM +0400, Konstantin Khlebnikov wrote:
>> This patch fixes all of them.
>
> It seems to have rendered virtio_balloon completely ineffective without
> CONFIG_COMPACTION and CONFIG_BALLOON_COMPACTION, even for the case that I'm
> expanding the memory available to my VM.
What do you mean by ineffective?
That it cannot handle fragmentation? I saw that without compaction
ballooning works even better:
it allocates pages without GFP_MOVABLE and buddy allocator returns
much less scattered pages.
>
> Was this intended? Should Kconfig be updated so that VIRTIO_BALLOON depends on
> BALLOON_COMPACTION now?
Nope, this is independent feature.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists