Re: [PATCH v1 1/6] mm: Adjust shuffle code to allow for future coalescing

2019-06-28 Thread Alexander Duyck
On Tue, Jun 25, 2019 at 12:56 AM David Hildenbrand wrote: > > On 20.06.19 00:33, Alexander Duyck wrote: > > From: Alexander Duyck > > > > 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

Re: [PATCH v1 1/6] mm: Adjust shuffle code to allow for future coalescing

2019-06-25 Thread Dave Hansen
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

Re: [PATCH v1 1/6] mm: Adjust shuffle code to allow for future coalescing

2019-06-25 Thread Dave Hansen
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

Re: [PATCH v1 1/6] mm: Adjust shuffle code to allow for future coalescing

2019-06-25 Thread David Hildenbrand
On 20.06.19 00:33, Alexander Duyck wrote: > From: Alexander Duyck > > 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

[PATCH v1 1/6] mm: Adjust shuffle code to allow for future coalescing

2019-06-19 Thread Alexander Duyck
From: Alexander Duyck 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