All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] [RFC] move 'struct page' into its own header
Date: Thu, 16 Dec 2004 22:25:13 +0000	[thread overview]
Message-ID: <20041216222513.GA15451@infradead.org> (raw)
In-Reply-To: <E1Cf3jM-00034h-00@kernel.beaverton.ibm.com>

On Thu, Dec 16, 2004 at 02:04:15PM -0800, Dave Hansen wrote:
> 
> There are currently 24 places in the tree where struct page is
> predeclared.  However, a good number of these places also have to
> do some kind of arithmetic on it, and end up using macros because
> static inlines wouldn't have the type fully definied at
> compile-time.
> 
> But, in reality, struct page has very few dependencies on outside
> macros or functions, and doesn't really need to be a part of the
> header include mess which surrounds many of the VM headers.
> 
> So, put 'struct page' into structpage.h, along with a nasty comment
> telling everyone to keep their grubby mitts out of the file.
> 
> Now, we can use static inlines for almost any 'struct page'
> operations with no problems, and get rid of many of the 
> predeclarations.


What about calling it page.h?  structfoo.h sounds like a really strange
name.  And while you're at it page-flags.h should probably be merged into
it.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] [RFC] move 'struct page' into its own header
Date: Thu, 16 Dec 2004 22:25:13 +0000	[thread overview]
Message-ID: <20041216222513.GA15451@infradead.org> (raw)
In-Reply-To: <E1Cf3jM-00034h-00@kernel.beaverton.ibm.com>

On Thu, Dec 16, 2004 at 02:04:15PM -0800, Dave Hansen wrote:
> 
> There are currently 24 places in the tree where struct page is
> predeclared.  However, a good number of these places also have to
> do some kind of arithmetic on it, and end up using macros because
> static inlines wouldn't have the type fully definied at
> compile-time.
> 
> But, in reality, struct page has very few dependencies on outside
> macros or functions, and doesn't really need to be a part of the
> header include mess which surrounds many of the VM headers.
> 
> So, put 'struct page' into structpage.h, along with a nasty comment
> telling everyone to keep their grubby mitts out of the file.
> 
> Now, we can use static inlines for almost any 'struct page'
> operations with no problems, and get rid of many of the 
> predeclarations.


What about calling it page.h?  structfoo.h sounds like a really strange
name.  And while you're at it page-flags.h should probably be merged into
it.
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-12-16 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 22:04 [patch] [RFC] move 'struct page' into its own header Dave Hansen
2004-12-16 22:04 ` Dave Hansen
2004-12-16 22:25 ` Christoph Hellwig [this message]
2004-12-16 22:25   ` Christoph Hellwig
2004-12-16 22:46   ` Dave Hansen
2004-12-16 22:46     ` Dave Hansen
2004-12-16 23:06     ` Russell King
2004-12-16 23:06       ` Russell King

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=20041216222513.GA15451@infradead.org \
    --to=hch@infradead.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.