Re: [PATCH 2/2] mm: rename page dtor functions to {compound,huge,transhuge}_page__dtor

2017-10-17 Thread Michal Hocko
On Tue 17-10-17 14:22:14, Kirill A. Shutemov wrote: > On Tue, Oct 17, 2017 at 12:22:03PM +0200, Michal Hocko wrote: > > On Mon 16-10-17 17:19:17, changbin...@intel.com wrote: > > > From: Changbin Du > > > > > > The current name free_{huge,transhuge}_page are paired with >

Re: [PATCH 2/2] mm: rename page dtor functions to {compound,huge,transhuge}_page__dtor

2017-10-17 Thread Kirill A. Shutemov
On Tue, Oct 17, 2017 at 12:22:03PM +0200, Michal Hocko wrote: > On Mon 16-10-17 17:19:17, changbin...@intel.com wrote: > > From: Changbin Du > > > > The current name free_{huge,transhuge}_page are paired with > > alloc_{huge,transhuge}_page functions, but the actual page

Re: [PATCH 2/2] mm: rename page dtor functions to {compound,huge,transhuge}_page__dtor

2017-10-17 Thread Michal Hocko
On Mon 16-10-17 17:19:17, changbin...@intel.com wrote: > From: Changbin Du > > The current name free_{huge,transhuge}_page are paired with > alloc_{huge,transhuge}_page functions, but the actual page free > function is still free_page() which will indirectly call >

Re: [PATCH 2/2] mm: rename page dtor functions to {compound,huge,transhuge}_page__dtor

2017-10-17 Thread Anshuman Khandual
On 10/16/2017 02:49 PM, changbin...@intel.com wrote: > From: Changbin Du > > The current name free_{huge,transhuge}_page are paired with > alloc_{huge,transhuge}_page functions, but the actual page free > function is still free_page() which will indirectly call >