[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141113064035.GB18369@js1304-P5Q-DELUXE>
Date: Thu, 13 Nov 2014 15:40:35 +0900
From: Joonsoo Kim <iamjoonsoo.kim@....com>
To: Dave Hansen <dave@...1.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>,
Johannes Weiner <hannes@...xchg.org>,
Minchan Kim <minchan@...nel.org>,
Alexander Nyberg <alexn@....su.se>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Michal Nazarewicz <mina86@...a86.com>,
Jungsoo Son <jungsoo.son@....com>,
Ingo Molnar <mingo@...hat.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/5] mm/page_ext: resurrect struct page extending
code for debugging
On Wed, Nov 12, 2014 at 08:33:40AM -0800, Dave Hansen wrote:
> On 11/12/2014 12:27 AM, Joonsoo Kim wrote:
> > @@ -1092,6 +1096,14 @@ struct mem_section {
> >
> > /* See declaration of similar field in struct zone */
> > unsigned long *pageblock_flags;
> > +#ifdef CONFIG_PAGE_EXTENSION
> > + /*
> > + * If !SPARSEMEM, pgdat doesn't have page_ext pointer. We use
> > + * section. (see page_ext.h about this.)
> > + */
> > + struct page_ext *page_ext;
> > + unsigned long pad;
> > +#endif
>
> Will the distributions be amenable to enabling this? If so, I'm all for
> it if it gets us things like page_owner at runtime.
Yes, I hope so.
At least, I can make it default to our product. But, how distributions
will do is beyond my power. :)
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists