public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new kernel patch (relative to 2.4.18)
Date: Wed, 08 May 2002 20:29:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905557@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905293@msgid-missing>

>>>>> On Wed, 8 May 2002 14:43:42 -0500 (CDT), Jack Steiner <steiner@sgi.com> said:

  Jack> I dont think the latest discontig patch makes any assumptions
  Jack> about memory layout and where memory holes appear. This info
  Jack> is passed to the kernel in the ACPI tables.  There are also
  Jack> platform specific macros defined in a platform mmzone_xxx file
  Jack> that are used to provide platform abstractions.

The discontig patch would be a lot more acceptable to me if it didn't
drag in all the other NUMA stuff.  As it stands, it's overkill.

Also, the discontig patch has a buch of hardcoded limits (e.g.,
maximum number of nodes, max. "clumps" per node, etc.), so it's really
not all that general by itself.  It's just more tweakable.

  Jack> Can the zx1 platform provide the necessary ACPI tables?? If
  Jack> so, it would be interesting to see what the asm/mmzone_zx1.h
  Jack> file would look like (assuming it could be done).

All the info needed for discontiguous memory is in the EFI memory
table.  The ACPI tables should be needed only for locality info, which
has very little to do with discontinuity (one usually implies the
other, but not vice versa).

  >>  There have been discussions on this topic on the lkml recently
  >> and different solutions have been proposed.  I don't really care
  >> too much which solution is used in the end as long as it is able
  >> to accommodate arbitrary physical layouts and has no dramatic
  >> performance impact.

  Jack> Agree. I'm certainly happy with any approach that satisfies
  Jack> these requirements.

I think it would be interesting to see a discontig patch which leaves
out all the NUMA stuff.  I really believe it would actually help clean
up that patch a lot.

	--david


  parent reply	other threads:[~2002-05-08 20:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  5:02 [Linux-ia64] new kernel patch (relative to 2.5.7-pre1) David Mosberger
2002-04-10 21:42 ` [Linux-ia64] new kernel patch (relative to 2.4.18) David Mosberger
2002-04-10 22:23 ` Stephane Eranian
2002-04-11 18:22 ` Chris McDermott
2002-04-11 20:04 ` Saxena, Sunil
2002-04-11 23:49 ` [Linux-ia64] new kernel patch (relative to 2.5.8-pre3) David Mosberger
2002-04-12  0:46 ` Greg KH
2002-04-12  0:49 ` David Mosberger
2002-04-12  1:01 ` Jes Sorensen
2002-04-12  1:04 ` Greg KH
2002-04-12  2:15 ` David Mosberger
2002-04-12  3:50 ` Greg KH
2002-04-12  4:43 ` Greg KH
2002-04-12  5:31 ` David Mosberger
2002-04-22  7:02 ` [Linux-ia64] new kernel patch (relative to 2.4.18) Zach, Yoav
2002-04-22 14:47 ` n0ano
2002-04-22 14:57 ` Andreas Schwab
2002-04-22 15:34 ` David Mosberger
2002-04-22 15:40 ` n0ano
2002-05-02 17:41 ` Steffen Persvold
2002-05-03  7:35 ` Ross Elliott
2002-05-03 17:23 ` David Mosberger
2002-05-03 23:36 ` Steffen Persvold
2002-05-08 17:49 ` David Mosberger
2002-05-08 18:25 ` Luck, Tony
2002-05-08 19:21 ` David Mosberger
2002-05-08 19:43 ` Jack Steiner
2002-05-08 20:29 ` David Mosberger [this message]
2002-05-08 23:26 ` 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=marc-linux-ia64-105590701905557@msgid-missing \
    --to=davidm@napali.hpl.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