From: Dave Hansen <dave@sr71.net>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Minchan Kim <minchan@kernel.org>,
Alexander Nyberg <alexn@dsv.su.se>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Michal Nazarewicz <mina86@mina86.com>,
Jungsoo Son <jungsoo.son@lge.com>, Ingo Molnar <mingo@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] mm/page_ext: resurrect struct page extending code for debugging
Date: Wed, 12 Nov 2014 08:33:40 -0800 [thread overview]
Message-ID: <54638BE4.3080509@sr71.net> (raw)
In-Reply-To: <1415780835-24642-2-git-send-email-iamjoonsoo.kim@lge.com>
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.
If not, this becomes of much more questionable utility.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Minchan Kim <minchan@kernel.org>,
Alexander Nyberg <alexn@dsv.su.se>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Michal Nazarewicz <mina86@mina86.com>,
Jungsoo Son <jungsoo.son@lge.com>, Ingo Molnar <mingo@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] mm/page_ext: resurrect struct page extending code for debugging
Date: Wed, 12 Nov 2014 08:33:40 -0800 [thread overview]
Message-ID: <54638BE4.3080509@sr71.net> (raw)
In-Reply-To: <1415780835-24642-2-git-send-email-iamjoonsoo.kim@lge.com>
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.
If not, this becomes of much more questionable utility.
next prev parent reply other threads:[~2014-11-12 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 8:27 [RFC PATCH 0/5] Resurrect and use struct page extension for some debugging features Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
2014-11-12 8:27 ` [RFC PATCH 1/5] mm/page_ext: resurrect struct page extending code for debugging Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
2014-11-12 16:33 ` Dave Hansen [this message]
2014-11-12 16:33 ` Dave Hansen
2014-11-13 6:40 ` Joonsoo Kim
2014-11-13 6:40 ` Joonsoo Kim
2014-11-13 20:40 ` Andrew Morton
2014-11-13 20:40 ` Andrew Morton
2014-11-14 0:14 ` Joonsoo Kim
2014-11-14 0:14 ` Joonsoo Kim
2014-11-12 8:27 ` [RFC PATCH 2/5] mm/debug-pagealloc: prepare boottime configurable on/off Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
2014-11-12 8:27 ` [RFC PATCH 3/5] mm/debug-pagealloc: make debug-pagealloc boottime configurable Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
2014-11-12 8:27 ` [RFC PATCH 4/5] stacktrace: support snprint Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
2014-11-12 8:27 ` [RFC PATCH 5/5] mm/page_owner: keep track of page owners Joonsoo Kim
2014-11-12 8:27 ` Joonsoo Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54638BE4.3080509@sr71.net \
--to=dave@sr71.net \
--cc=akpm@linux-foundation.org \
--cc=alexn@dsv.su.se \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jungsoo.son@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.