public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Franck <vagabon.xyz@gmail.com>, Andrew Morton <akpm@osdl.org>,
	Mel Gorman <mel@skynet.ie>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Clean up the bootmem allocator
Date: Tue, 27 Jun 2006 10:23:29 +0200	[thread overview]
Message-ID: <44A0EB01.9090809@innova-card.com> (raw)
In-Reply-To: <1151344691.10877.44.camel@localhost.localdomain>

Dave Hansen wrote:
> On Mon, 2006-06-26 at 15:11 +0200, Franck Bui-Huu wrote:
>> This patch does _only_ some cleanup in the bootmem allocator by:
> ...
>>  include/linux/bootmem.h |  101 ++++++++++++++----------
>>  mm/bootmem.c            |  195 ++++++++++++++++++++++++++---------------------
>>  2 files changed, 167 insertions(+), 129 deletions(-)
> 
> I'm always suspicious of "cleanups" which add more code than they remove ;)
> 

it's mainly due to the "80 columns limit" changes

>>         - following the kernel coding style conventions
> 
> Above everything else, this probably needs to be in its very own patch,
> where it is trivially verifiable. 
> 
>>         - using pfn/page conversion macros
>>         - removing some not needed parentheses
>>         - removing some useless included headers
>>         - limiting to 80 column width
> 
> In general, I think there is some good stuff in here.  However, instead
> of concentrating on "kernel coding style conventions" and numeric (80
> column) guidelines, I really hope that people consider _readability_
> when modifying this code.  I don't think this patch makes the code much
> more readable.
> 

well, IMHO using pfn/page conversion macros makes the code more readable.

> That said, there are some nice helper function in here.  Would you be
> able to break this patch up into maybe 10 or 15 smaller patches?  I have
> the feeling it will be easier to find the good bits then.
> 

ok I'll split that.

>> It also removes __init tags in the header file and hopefully make it
>> easier to read. 
> 
> I think I kinda like when these are present in headers.  I usually
> stumble across the header declarations before I do the ones in the .c
> files, and it is always nice to see the header visually _matching_
> the .c file, and how the variable is intended to be used
> 

see Andrew's comments...

		Franck


  parent reply	other threads:[~2006-06-27  8:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 13:11 [PATCH] Clean up the bootmem allocator Franck Bui-Huu
2006-06-26 17:58 ` Dave Hansen
2006-06-26 18:10   ` Andrew Morton
2006-06-27  8:23   ` Franck Bui-Huu [this message]
2006-06-27 12:53   ` [PATCH 0/7] " Franck Bui-Huu
2006-06-27 12:53   ` [PATCH 1/7] bootmem: remove useless __init in header file Franck Bui-Huu
2006-06-27 17:17     ` Dave Hansen
2006-06-27 19:18       ` Franck Bui-Huu
2006-06-27 12:53   ` [PATCH 2/7] bootmem: mark link_bootmem() as part of the __init section Franck Bui-Huu
2006-06-27 17:17     ` Dave Hansen
2006-06-27 19:18       ` Franck Bui-Huu
2006-06-27 12:54   ` [PATCH 3/7] bootmem: remove useless parentheses in bootmem header file Franck Bui-Huu
2006-06-27 12:54   ` [PATCH 4/7] bootmem: limit to 80 columns width Franck Bui-Huu
2006-06-27 12:54   ` [PATCH 5/7] bootmem: remove useless headers inclusions Franck Bui-Huu
2006-06-27 12:54   ` [PATCH 6/7] bootmem: use pfn/page conversion macros Franck Bui-Huu
2006-06-27 19:26     ` Dave Hansen
2006-06-29  7:53       ` Franck Bui-Huu
2006-06-27 12:54   ` [PATCH 7/7] bootmem: miscellaneous coding style fixes Franck Bui-Huu
2006-06-27 17:26     ` Dave Hansen
2006-06-27 19:22       ` Franck Bui-Huu
2006-06-27 22:35         ` Randy.Dunlap

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=44A0EB01.9090809@innova-card.com \
    --to=vagabon.xyz@gmail.com \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@skynet.ie \
    /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