Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1459798
| From | Sergey Senozhatsky <sergey.senozhatsky@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/5] mm/debug_pagealloc: don't allocate page_ext if we don't use guard page |
| Date | 2016-08-10 22:20 +0200 |
| Message-ID | <s4I8N-1sK-3@gated-at.bofh.it> (permalink) |
| References | <s4GgH-79-61@gated-at.bofh.it> <s4I8N-1sK-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On (08/10/16 15:16), js1304@gmail.com wrote: > From: Joonsoo Kim <iamjoonsoo.kim@lge.com> > > What debug_pagealloc does is just mapping/unmapping page table. > Basically, it doesn't need additional memory space to memorize something. > But, with guard page feature, it requires additional memory to distinguish > if the page is for guard or not. Guard page is only used when > debug_guardpage_minorder is non-zero so this patch removes additional > memory allocation (page_ext) if debug_guardpage_minorder is zero. > > It saves memory if we just use debug_pagealloc and not guard page. > > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com> -ss
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH 2/5] mm/debug_pagealloc: don't allocate page_ext if we don't use guard page Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-08-10 22:20 +0200
csiph-web