[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8287bfe-8b34-895c-eff2-c88d0a3f76ae@intel.com>
Date: Tue, 25 Jun 2019 11:26:46 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Alexander Duyck <alexander.duyck@...il.com>, nitesh@...hat.com,
kvm@...r.kernel.org, david@...hat.com, mst@...hat.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
akpm@...ux-foundation.org
Cc: yang.zhang.wz@...il.com, pagupta@...hat.com, riel@...riel.com,
konrad.wilk@...cle.com, lcapitulino@...hat.com,
wei.w.wang@...el.com, aarcange@...hat.com, pbonzini@...hat.com,
dan.j.williams@...el.com, alexander.h.duyck@...ux.intel.com
Subject: Re: [PATCH v1 1/6] mm: Adjust shuffle code to allow for future
coalescing
On 6/19/19 3:33 PM, Alexander Duyck wrote:
> This patch is meant to move the head/tail adding logic out of the shuffle
> code and into the __free_one_page function since ultimately that is where
> it is really needed anyway. By doing this we should be able to reduce the
> overhead and can consolidate all of the list addition bits in one spot.
This looks like a sane cleanup that can stand on its own. It gives nice
names (buddy_merge_likely()) to things that were just code blobs before.
Reviewed-by: Dave Hansen <dave.hansen@...el.com>
Powered by blists - more mailing lists