From: Erich Focht <efocht@ess.nec.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] discontig-ia64 and acpi-numa patches
Date: Thu, 08 Aug 2002 16:40:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905926@msgid-missing> (raw)
Hi!
This is a second attempt to split the discontig-ia64 patch. The result
is on sourceforge at:
http://sf.net/project/showfiles.php?group_id=35660&release_id=103977
There are three patches for 2.4.18 + ia64-020722 :
The main change: the previous core part was splitted, the ACPI
initialization was changed into arch-dependent and -independent parts.
01_discontig-acpi-numa.diff : required, provides ACPI initialization
of NUMA specific variables.
02_discontig-core.diff : core part providing discontigmem
functionality.
03_discontig-krel-krep.diff : optional part of discontigmem, provides
kernel relocation and replication. Required
on SGI SN.
You can pply additionally one of the zonelist patches and the
discontig-proc_info patch from the previous release.
The ACPI part of the patch has been radically changed, it fits into the
structure (arch-dependend + independent) proposed by Tak Kouchi. This
part is functional and useful even without discontigmem. It basically
gathers the NUMA related information and puts it into the structures
node_memblk, node_cpuid, numa_slit. These contain, respectively, the
affinity information of memory blocks, cpus and the locality information
of the nodes. The code is quite arch-independent and could be used by
other architectures which have ACPI SRAT/SLIT information.
The patches are building blocks for the discontigmem needs on IA64:
NEC Azusa/Asama, DIG64: required: acpi-numa + core,
optional: krel-krep
SGI SN : required: acpi + core + krel-krep
For those involved into the DIG-discontigmem development: I've set
CHUNKSIZE and CLUMPSIZE to be equal in mmzone_dig_numa.h. This avoids
some pitfalls and we expect anyway contiguous physical memory here,
so it doesn't matter.
The patch is tested on 4 node Azusa. I left out the phoney SRAT/SLIT
tables, they are now slightly more difficult to parse without extra code,
so I'm afraid right now there's no way to test pseudo-NUMA on BigSur
or Tiger.
Best regards,
Erich
reply other threads:[~2002-08-08 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105590701905926@msgid-missing \
--to=efocht@ess.nec.de \
--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.