[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070316.135821.125896069.davem@davemloft.net>
Date: Fri, 16 Mar 2007 13:58:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: clameter@....com
Cc: mbligh@...igh.org, andi@...stfloor.org, rostedt@...dmis.org,
torvalds@...ux-foundation.org, mingo@...e.hu,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
chrisw@...s-sol.org, rusty@...tcorp.com.au, glommer@...il.com,
apw@...dowen.org
Subject: Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 -
Take 2
From: Christoph Lameter <clameter@....com>
Date: Fri, 16 Mar 2007 13:56:13 -0700 (PDT)
> On Fri, 16 Mar 2007, David Miller wrote:
>
> > From: Christoph Lameter <clameter@....com>
> > Date: Fri, 16 Mar 2007 13:48:58 -0700 (PDT)
> >
> > > Please read my posts to linux-mm on that subject. We discussed it last
> > > year in detail and the agreement was that the sparsemem crud needs to be
> > > taken out. Kame-san posted patches to do that.
> >
> > Please don't do that, sparsemem works very well on sparc64 and I
> > like the flexibility it gives me.
>
> I am not sure what flexibility you are talking about? The modification are
> to make sparsemem support virtual memmap as one option. See Kame-san's
> posts. There is no regression here its just cutting out the overhead of
> sparsmem from within.
I would really appreciate a posting that explains what exactly is
going on being sent to linux-arch, this is the first time I myself am
even aware of this idea and work.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists