All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger-Tang <David.Mosberger@acm.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/4] V4 ia64 SPARSEMEM
Date: Tue, 27 Sep 2005 01:20:08 +0000	[thread overview]
Message-ID: <ed5aea43050926182024b7e66c@mail.gmail.com> (raw)
In-Reply-To: <20050922161418.GW16066@localhost.localdomain>

On 9/26/05, Luck, Tony <tony.luck@intel.com> wrote:

> >Long term should SPARSEMEM become the default and DISCONTIG+VIRTUAL_MEM_MAP
> >be obsoleted then we could remove the config files.
>
> If benchmarks show no difference, then I'll consolidate the
> configuration options.  I still think that VIRTUAL_MEM_MAP
> has a great deal of elegance to it ... auto-sizing to just
> about any degree of sparseness, but I think we need to
> simplify.

Benchmarks cannot prove the absence of a performance difference in
*general*, they can only do that for specific tests and workloads. 
So, unless SPARSEMEM actually performs *better* on some benchmarks
(and no worse on others), the proper course seems to be to stick with
VIRTUAL_MEM_MAP where SPARSEMEM isn't needed.

I have voice my objection in the past to Bob's suggestion that
SPARSEMEM should replace VIRTUAL_MEM_MAP and since then I haven't seen
any convincing argument why that should be the case, so I do not
understand why Bob keeps bringing that up.

  --david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536

  parent reply	other threads:[~2005-09-27  1:20 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 [this message]
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
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=ed5aea43050926182024b7e66c@mail.gmail.com \
    --to=david.mosberger@acm.org \
    --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 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.