public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/4] V4 ia64 SPARSEMEM
Date: Tue, 27 Sep 2005 14:10:26 +0000	[thread overview]
Message-ID: <20050927141026.GP16066@localhost.localdomain> (raw)
In-Reply-To: <20050922161418.GW16066@localhost.localdomain>

Jack Steiner wrote:	[Tue Sep 27 2005, 08:45:00AM EDT]
> > We could be more aggressive than other arches but still follow the cautious
> > path.  I'm reluctant to suggest this but adding a couple of default 
> > configuration files with SPARSEMEM might be useful.  Perhaps 
> > sn2_defconfig_sparsemem and defconfig_sparsemem. 
> > 
> 
> Although many developers at SGI use SN-specific configuration files,
> customers run SuSE & RH and use kernels built with the GENERIC config 
> since the kernel binary runs on all hardware vendors platforms.
> It is important to make the default config file run efficiently
> on all platforms.
okay.
> 
> I haven't looked in detail at SPARSEMEM recently - is one config
> file for ALL hardware platforms easy to do without significantly 
> compromising performance of any individual platform?
I don't know whether that can be achieved.  We've really done limited 
performance comparisons. It would have to be investigated.
> 
> 
> -- 
> Jack
bob

  parent reply	other threads:[~2005-09-27 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 16:14 [PATCH 0/4] V4 ia64 SPARSEMEM Bob Picco
2005-09-26 20:40 ` Luck, Tony
2005-09-26 22:23 ` Luck, Tony
2005-09-26 23:35 ` Bob Picco
2005-09-26 23:40 ` Bob Picco
2005-09-27  0:03 ` Luck, Tony
2005-09-27  1:20 ` David Mosberger-Tang
2005-09-27  4:53 ` Yasunori Goto
2005-09-27 12:45 ` Jack Steiner
2005-09-27 14:09 ` Bob Picco
2005-09-27 14:10 ` Bob Picco [this message]
2005-09-27 19:22 ` Bob Picco
2005-09-27 22:00 ` Luck, Tony

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=20050927141026.GP16066@localhost.localdomain \
    --to=bob.picco@hp.com \
    --cc=linux-ia64@vger.kernel.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