public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Adrian Bunk <bunk@stusta.de>, Russell King <rmk@arm.uk.linux.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] mm/swap_state.c: unexport swapper_space
Date: Sun, 6 Mar 2005 22:49:12 +0000	[thread overview]
Message-ID: <20050306224912.GE5827@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0503061515200.19898@goblin.wat.veritas.com>

On Sun, Mar 06, 2005 at 03:28:19PM +0000, Hugh Dickins wrote:
> immediately on demand).  It's used by the inline page_mapping() in
> include/linux/mm.h, which _was_ used by various arch cacheflushing
> inlines, which could reasonably be called from modular filesystems.
> 
> I think those architectures hit the missed export when the dependence
> on &swapper_space got added to page_mapping(), the export was soon
> added to mainline, but meanwhile they moved their inlines out-of-line
> - perhaps temporarily, but not yet reverted.
> 
> Better leave it exported so long as page_mapping is using it.

I disagree.  swapper_state is far too much of an internal detail to be
exported.  I argued that way when page_mapping was changed to use it and
that's why the architectures moved their helpers out of line.
Looks like the exported unfortunately got added anyway although we settled
that discussion.


  reply	other threads:[~2005-03-06 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 14:47 [2.6 patch] mm/swap_state.c: unexport swapper_space Adrian Bunk
2005-03-06 15:28 ` Hugh Dickins
2005-03-06 22:49   ` Christoph Hellwig [this message]
2005-03-08  9:09     ` Russell King
2005-03-08 11:45       ` Hugh Dickins
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25  1:11 Adrian Bunk

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=20050306224912.GE5827@infradead.org \
    --to=hch@infradead.org \
    --cc=bunk@stusta.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.uk.linux.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