Messages in this thread | | | Subject | Re: [PATCH v2 2/3] mm, page_owner: decouple freeing stack trace from debug_pagealloc | From | Vlastimil Babka <> | Date | Tue, 1 Oct 2019 14:32:56 +0200 |
| |
On 10/1/19 2:26 PM, Qian Cai wrote: > On Tue, 2019-10-01 at 14:51 +0300, Kirill A. Shutemov wrote: >> On Tue, Oct 01, 2019 at 10:07:44AM +0200, Vlastimil Babka wrote: >>> On 10/1/19 1:49 AM, Qian Cai wrote: >> >> DEBUG_PAGEALLOC is much more intrusive debug option. Not all architectures >> support it in an efficient way. Some require hibernation. >> >> I don't see a reason to tie these two option together. > > Make sense. How about page_owner=on will have page_owner_free=on by default? > That way we don't need the extra parameter.
There were others that didn't want that overhead (memory+cpu) always. So the last version is as flexible as we can get, IMHO, before approaching bikeshed territory. It's just another parameter.
| |