All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: apw@shadowen.org
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	linux-mm <linux-mm@kvack.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: max_mapnr config option
Date: Fri, 23 May 2008 21:52:12 +0200	[thread overview]
Message-ID: <87bq2wol1v.fsf@saeurebad.de> (raw)
In-Reply-To: <20080523130935.GA23176@shadowen.org> (apw@shadowen.org's message of "Fri, 23 May 2008 14:09:35 +0100")

Hi,

apw@shadowen.org writes:

> On Tue, Apr 08, 2008 at 11:51:38AM +0100, Andy Whitcroft wrote:
>> On Mon, Apr 07, 2008 at 12:03:53PM +0200, Johannes Weiner wrote:
>> > Hi,
>> > 
>> > Andy Whitcroft <apw@shadowen.org> writes:
>> > 
>> > > BUT.  Looking over the actual references, there is a lot of references
>> > > occuring out of show_mem implementations in the arches which may well break
>> > > unless they follow suit.  We also don't have any show_mem implementation
>> > > for sparsemem.  I will have a look at what can be trivially cleaned
>> > > up here.
>> > 
>> > Perhaps you might be interested in http://lkml.org/lkml/2008/4/4/ .
>> 
>> How annoying is that, you have done the same thing I've just done.  I'll
>> look at your version and base off that.
>
> Whatever happened to this series.  I don't see it committed anywhere.
> Do you have a latest stack I could rebase my max_mapnr fixes off?

I rebased it against Linus' current tree.  Not all parts of the `remove
redundant output of free swap space' series have yet trickled into
upstream, so what I give you includes that (it is minimal and should
have been part of this series in the first place).

When all of the previous series hit mainline I will repost this one.

Here is the quilt series:

  http://saeurebad.de/patches/generic-show_mem.tar

or unpacked without the `.tar'-suffix.

	Hannes

--
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>

      reply	other threads:[~2008-05-23 19:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1207340609.26869.20.camel@nimitz.home.sr71.net>
2008-04-10 10:33 ` max_mapnr config option Andy Whitcroft
2008-04-10 10:40   ` [PATCH 1/8] alpha: mem_map/max_mapnr -- init is FLATMEM use correct defines Andy Whitcroft
2008-04-10 10:41   ` [PATCH 2/8] arm: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 3/8] m32r: mem_map/max_mapnr -- definition is specific to FLATMEM Andy Whitcroft
2008-04-10 10:41   ` [PATCH 4/8] mips: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 5/8] parisc: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 6/8] powerpc: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 7/8] sparc64: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 8/8] mem_map/max_mapnr are specific to the FLATMEM memory model Andy Whitcroft
2008-06-02 15:13     ` Jeremy Fitzhardinge
     [not found] ` <20080407091756.GC17915@shadowen.org>
     [not found]   ` <87iqyuhth2.fsf@saeurebad.de>
     [not found]     ` <20080408105137.GD17915@shadowen.org>
2008-05-23 13:09       ` max_mapnr config option apw
2008-05-23 19:52         ` Johannes Weiner [this message]

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=87bq2wol1v.fsf@saeurebad.de \
    --to=hannes@saeurebad.de \
    --cc=apw@shadowen.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=jeremy@goop.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.