From: Paul Jackson <pj@sgi.com>
To: Alexander Nyberg <alexn@telia.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Some debugging patches on top of -mm
Date: Sat, 12 Nov 2005 03:13:20 -0800 [thread overview]
Message-ID: <20051112031320.40543ae4.pj@sgi.com> (raw)
In-Reply-To: <20050905195001.GA10223@localhost.localdomain>
Alexander,
This patch, known as page-owner-tracking-leak-detector.patch has
apparently been sitting in Andrew's *-mm for the last two months.
I just noticed it now, when reading mm/page_alloc.c.
I'd like to know if the #ifdef's and CONFIG_PAGE_OWNER specific code
can be removed from page_alloc.c, and put in a header file. Ideally,
you patch would add just one line to the __alloc_pages() code - a call
to set_page_owner() that either became no code (a static inline empty
function) or a call to your code, if this feature was CONFIG enabled.
The *.c files are where all the logic comes together, and it is vital
to the long term readability of these files that we avoid #ifdef's in
these files. Any one feature can be ifdef'd in, with seeming little
harm to the readability of the code (especially in the eyes of the
author of that particular bit of ifdef'd code ;). But imagine what
a deity-awful mess these files would be if we had all been doing that
over the years with our various favorite features.
I am not sure which header file - quite possibly in a new header
file just for this feature (unless others have the good sense to
recommend better.) Static inline code that is only called from
one place should work fine in a header file, at least technically.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-11-12 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 19:50 Some debugging patches on top of -mm Alexander Nyberg
2005-11-12 11:13 ` Paul Jackson [this message]
2005-11-12 20:26 ` Alexander Nyberg
2005-11-12 20:38 ` Paul Jackson
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=20051112031320.40543ae4.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox