From: Magnus Damm <magnus@valinux.co.jp>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Magnus Damm <magnus@valinux.co.jp>
Subject: [PATCH 00/07][RFC] i386: NUMA emulation
Date: Fri, 30 Sep 2005 16:33:15 +0900 (JST) [thread overview]
Message-ID: <20050930073232.10631.63786.sendpatchset@cherry.local> (raw)
These patches implement NUMA memory node emulation for regular i386 PC:s.
NUMA emulation could be used to provide coarse-grained memory resource control
using CPUSETS. Another use is as a test environment for NUMA memory code or
CPUSETS using an i386 emulator such as QEMU.
A similar feature was accepted for x86_64 back in 2.6.9. These patches use the
same config options and kernel command line parameters as the x86_64 code.
Patches that depend on 2.6.14-rc2:
[PATCH 01/07] i386: srat non acpi
[PATCH 02/07] i386: numa on non-smp
[PATCH 03/07] cpuset: smp or numa
Patches that depend on 2.6.14-rc2 plus two patches written by Dave Hansen and
posted to lkml and linux-mm at Sep 13 2005:
i386: consolidate discontig functions into normal ones
i386: move NUMA code into numa.c
[PATCH 04/07] i386: numa warning fix
[PATCH 05/07] i386: sparsemem on pc
[PATCH 06/07] i386: discontigmem on pc
[PATCH 07/07] i386: numa emulation on pc
To test, configure your i386 kernel with CONFIG_X86_PC, CONFIG_NUMA_EMU and
CONFIG_NUMA all set and pass "numa=fake=2" to the kernel to emulate two nodes.
Feedback is very appreciated.
Thanks,
/ magnus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2005-09-30 7:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 7:33 Magnus Damm [this message]
2005-09-30 7:33 ` [PATCH 01/07] i386: srat non acpi Magnus Damm, Magnus Damm
2005-09-30 7:33 ` [PATCH 02/07] i386: numa on non-smp Magnus Damm, Magnus Damm
2005-09-30 7:33 ` [PATCH 03/07] cpuset: smp or numa Magnus Damm, Magnus Damm
2005-09-30 7:33 ` [PATCH 04/07] i386: numa warning fix Magnus Damm, Isaku Yamahata
2005-09-30 7:33 ` [PATCH 05/07] i386: sparsemem on pc Magnus Damm, Magnus Damm
2005-09-30 15:25 ` Dave Hansen
2005-10-01 0:32 ` Magnus Damm
2005-09-30 7:33 ` [PATCH 06/07] i386: discontigmem " Magnus Damm, Magnus Damm
2005-09-30 7:33 ` [PATCH 07/07] i386: numa emulation " Magnus Damm, Isaku Yamahata
2005-09-30 18:55 ` Dave Hansen
2005-10-03 9:59 ` Magnus Damm
2005-10-03 16:16 ` Dave Hansen
2005-10-04 5:06 ` Magnus Damm
2005-10-04 7:52 ` Hirokazu Takahashi
2005-10-04 9:49 ` Magnus Damm
2005-09-30 15:23 ` [PATCH 00/07][RFC] i386: NUMA emulation Dave Hansen
2005-10-03 2:08 ` Magnus Damm
2005-10-03 7:34 ` David Lang
2005-10-03 10:02 ` Magnus Damm
2005-10-03 13:33 ` David Lang
2005-10-03 14:59 ` Martin J. Bligh
2005-10-03 15:03 ` David Lang
2005-10-03 15:08 ` Martin J. Bligh
2005-10-03 15:13 ` David Lang
2005-10-03 15:25 ` Martin J. Bligh
2005-10-03 15:32 ` David Lang
2005-10-03 15:54 ` Martin J. Bligh
2005-10-03 16:44 ` David Lang
2005-10-03 14:45 ` Martin J. Bligh
2005-10-03 14:49 ` David Lang
2005-10-03 3:21 ` Paul Jackson
2005-10-03 5:05 ` Magnus Damm
2005-10-03 5:26 ` Hirokazu Takahashi
2005-10-03 5:33 ` Paul Jackson
2005-10-03 5:59 ` Magnus Damm
2005-10-03 7:26 ` Paul Jackson
2005-10-03 5:34 ` Paul Jackson
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=20050930073232.10631.63786.sendpatchset@cherry.local \
--to=magnus@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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