public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Bob Picco <bob.picco@hp.com>, Andrew Morton <akpm@osdl.org>,
	Jack Steiner <steiner@sgi.com>,
	linux-arch@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>,
	"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Subject: Re: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 16:58:27 +0100	[thread overview]
Message-ID: <42B83923.1070202@shadowen.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F03BF8505@scsmsx401.amr.corp.intel.com>

Luck, Tony wrote:
>>Well ia64 SPARSEMEM hasn't been accepted yet by ia64.  I did test 
>>SPARSEMEM with recent -mm patches on ia64 (EXTREME) and x86_64 4 way 
>>Opteron (!EXTREME) with OSDL aim.
> 
> 
> I'm mostly worried about whether SGI are happy.  I saw the patches
> to add the "Extreme" option ... but have only seen minimal feedback
> from that.

I'd like to say here that the EXTREME stuff is faily new compared to the
other parts.  I'd be comfortable to push up the basic SPARSEMEM
implementation and leave the EXTREME in -mm for the moment I think there
will be other updates to it before we are done.

That said I'd like to also point out that SPARSEMEM is currently still
an additional memory model.  Any architecture that finds benefit from it
is welcome to use it, any that isn't yet finding it a benefit is not
being forced to use it.  Yes in a perfect world I'd like to minimise the
number of non 'standard' memory models there are for simplicity of code
etc, but it is not the intent that we force everyone into the same
staight jacket here.

-apw

  reply	other threads:[~2005-06-21 15:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 15:52 sparsemem patches in -mm Luck, Tony
2005-06-21 15:58 ` Andy Whitcroft [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-21 16:09 Luck, Tony
2005-06-21 16:17 ` Dave Hansen
2005-06-21  9:13 Andrew Morton
2005-06-21  9:50 ` Andi Kleen
2005-06-21 10:09   ` Andrew Morton
2005-06-21 15:49   ` Andy Whitcroft
2005-06-21 15:58     ` Andi Kleen
2005-06-21 11:00 ` Bob Picco
2005-06-21 15:57   ` Dave Hansen
2005-06-21 16:45     ` Bob Picco
2005-06-21 14:17 ` Matthew Wilcox
2005-06-21 15:51   ` Andy Whitcroft
2005-06-21 20:01     ` Andrew Morton
2005-06-21 23:39       ` Dave Hansen
2005-06-22  5:46 ` David S. Miller
2005-06-22  6:00   ` Andrew Morton
2005-07-27 22:42     ` David S. Miller
2005-06-23 22:48 ` Roman Zippel
2005-06-23 22:56   ` Dave Hansen
2005-06-23 23:53     ` Roman Zippel

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=42B83923.1070202@shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=bob.picco@hp.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=steiner@sgi.com \
    --cc=tony.luck@intel.com \
    /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