forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'for-linus' of git://one.firstfloor.org/home/andi/git/li…
…nux-2.6 * 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6: (231 commits) [PATCH] i386: Don't delete cpu_devs data to identify different x86 types in late_initcall [PATCH] i386: type may be unused [PATCH] i386: Some additional chipset register values validation. [PATCH] i386: Add missing !X86_PAE dependincy to the 2G/2G split. [PATCH] x86-64: Don't exclude asm-offsets.c in Documentation/dontdiff [PATCH] i386: avoid redundant preempt_disable in __unlazy_fpu [PATCH] i386: white space fixes in i387.h [PATCH] i386: Drop noisy e820 debugging printks [PATCH] x86-64: Fix allnoconfig error in genapic_flat.c [PATCH] x86-64: Shut up warnings for vfat compat ioctls on other file systems [PATCH] x86-64: Share identical video.S between i386 and x86-64 [PATCH] x86-64: Remove CONFIG_REORDER [PATCH] x86-64: Print type and size correctly for unknown compat ioctls [PATCH] i386: Remove copy_*_user BUG_ONs for (size < 0) [PATCH] i386: Little cleanups in smpboot.c [PATCH] x86-64: Don't enable NUMA for a single node in K8 NUMA scanning [PATCH] x86: Use RDTSCP for synchronous get_cycles if possible [PATCH] i386: Add X86_FEATURE_RDTSCP [PATCH] i386: Implement X86_FEATURE_SYNC_RDTSC on i386 [PATCH] i386: Implement alternative_io for i386 ... Fix up trivial conflict in include/linux/highmem.h manually. Signed-off-by: Linus Torvalds <[email protected]>
- Loading branch information
Showing
319 changed files
with
7,564 additions
and
10,400 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1745,8 +1745,9 @@ S: D-64295 | |
S: Germany | ||
|
||
N: Andi Kleen | ||
E: [email protected] | ||
D: network hacker, syncookies | ||
E: [email protected] | ||
U: http://www.halobates.de | ||
D: network, x86, NUMA, various hacks | ||
S: Schwalbenstr. 96 | ||
S: 85551 Ottobrunn | ||
S: Germany | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
---------------------------- | ||
|
||
H. Peter Anvin <[email protected]> | ||
Last update 2007-01-26 | ||
Last update 2007-03-06 | ||
|
||
On the i386 platform, the Linux kernel uses a rather complicated boot | ||
convention. This has evolved partially due to historical aspects, as | ||
|
@@ -35,9 +35,13 @@ Protocol 2.03: (Kernel 2.4.18-pre1) Explicitly makes the highest possible | |
initrd address available to the bootloader. | ||
|
||
Protocol 2.04: (Kernel 2.6.14) Extend the syssize field to four bytes. | ||
|
||
Protocol 2.05: (Kernel 2.6.20) Make protected mode kernel relocatable. | ||
Introduce relocatable_kernel and kernel_alignment fields. | ||
|
||
Protocol 2.06: (Kernel 2.6.22) Added a field that contains the size of | ||
the boot command line | ||
|
||
|
||
**** MEMORY LAYOUT | ||
|
||
|
@@ -133,6 +137,8 @@ Offset Proto Name Meaning | |
022C/4 2.03+ initrd_addr_max Highest legal initrd address | ||
0230/4 2.05+ kernel_alignment Physical addr alignment required for kernel | ||
0234/1 2.05+ relocatable_kernel Whether kernel is relocatable or not | ||
0235/3 N/A pad2 Unused | ||
0238/4 2.06+ cmdline_size Maximum size of the kernel command line | ||
|
||
(1) For backwards compatibility, if the setup_sects field contains 0, the | ||
real value is 4. | ||
|
@@ -233,6 +239,12 @@ filled out, however: | |
if your ramdisk is exactly 131072 bytes long and this field is | ||
0x37FFFFFF, you can start your ramdisk at 0x37FE0000.) | ||
|
||
cmdline_size: | ||
The maximum size of the command line without the terminating | ||
zero. This means that the command line can contain at most | ||
cmdline_size characters. With protocol version 2.05 and | ||
earlier, the maximum size was 255. | ||
|
||
|
||
**** THE KERNEL COMMAND LINE | ||
|
||
|
@@ -241,11 +253,10 @@ loader to communicate with the kernel. Some of its options are also | |
relevant to the boot loader itself, see "special command line options" | ||
below. | ||
|
||
The kernel command line is a null-terminated string currently up to | ||
255 characters long, plus the final null. A string that is too long | ||
will be automatically truncated by the kernel, a boot loader may allow | ||
a longer command line to be passed to permit future kernels to extend | ||
this limit. | ||
The kernel command line is a null-terminated string. The maximum | ||
length can be retrieved from the field cmdline_size. Before protocol | ||
version 2.06, the maximum was 255 characters. A string that is too | ||
long will be automatically truncated by the kernel. | ||
|
||
If the boot protocol version is 2.02 or later, the address of the | ||
kernel command line is given by the header field cmd_line_ptr (see | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
Using numa=fake and CPUSets for Resource Management | ||
Written by David Rientjes <[email protected]> | ||
|
||
This document describes how the numa=fake x86_64 command-line option can be used | ||
in conjunction with cpusets for coarse memory management. Using this feature, | ||
you can create fake NUMA nodes that represent contiguous chunks of memory and | ||
assign them to cpusets and their attached tasks. This is a way of limiting the | ||
amount of system memory that are available to a certain class of tasks. | ||
|
||
For more information on the features of cpusets, see Documentation/cpusets.txt. | ||
There are a number of different configurations you can use for your needs. For | ||
more information on the numa=fake command line option and its various ways of | ||
configuring fake nodes, see Documentation/x86_64/boot-options.txt. | ||
|
||
For the purposes of this introduction, we'll assume a very primitive NUMA | ||
emulation setup of "numa=fake=4*512,". This will split our system memory into | ||
four equal chunks of 512M each that we can now use to assign to cpusets. As | ||
you become more familiar with using this combination for resource control, | ||
you'll determine a better setup to minimize the number of nodes you have to deal | ||
with. | ||
|
||
A machine may be split as follows with "numa=fake=4*512," as reported by dmesg: | ||
|
||
Faking node 0 at 0000000000000000-0000000020000000 (512MB) | ||
Faking node 1 at 0000000020000000-0000000040000000 (512MB) | ||
Faking node 2 at 0000000040000000-0000000060000000 (512MB) | ||
Faking node 3 at 0000000060000000-0000000080000000 (512MB) | ||
... | ||
On node 0 totalpages: 130975 | ||
On node 1 totalpages: 131072 | ||
On node 2 totalpages: 131072 | ||
On node 3 totalpages: 131072 | ||
|
||
Now following the instructions for mounting the cpusets filesystem from | ||
Documentation/cpusets.txt, you can assign fake nodes (i.e. contiguous memory | ||
address spaces) to individual cpusets: | ||
|
||
[root@xroads /]# mkdir exampleset | ||
[root@xroads /]# mount -t cpuset none exampleset | ||
[root@xroads /]# mkdir exampleset/ddset | ||
[root@xroads /]# cd exampleset/ddset | ||
[root@xroads /exampleset/ddset]# echo 0-1 > cpus | ||
[root@xroads /exampleset/ddset]# echo 0-1 > mems | ||
|
||
Now this cpuset, 'ddset', will only allowed access to fake nodes 0 and 1 for | ||
memory allocations (1G). | ||
|
||
You can now assign tasks to these cpusets to limit the memory resources | ||
available to them according to the fake nodes assigned as mems: | ||
|
||
[root@xroads /exampleset/ddset]# echo $$ > tasks | ||
[root@xroads /exampleset/ddset]# dd if=/dev/zero of=tmp bs=1024 count=1G | ||
[1] 13425 | ||
|
||
Notice the difference between the system memory usage as reported by | ||
/proc/meminfo between the restricted cpuset case above and the unrestricted | ||
case (i.e. running the same 'dd' command without assigning it to a fake NUMA | ||
cpuset): | ||
Unrestricted Restricted | ||
MemTotal: 3091900 kB 3091900 kB | ||
MemFree: 42113 kB 1513236 kB | ||
|
||
This allows for coarse memory management for the tasks you assign to particular | ||
cpusets. Since cpusets can form a hierarchy, you can create some pretty | ||
interesting combinations of use-cases for various classes of tasks for your | ||
memory management needs. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1617,7 +1617,7 @@ S: Maintained | |
|
||
HPET: x86_64 | ||
P: Andi Kleen and Vojtech Pavlik | ||
M: [email protected] and [email protected] | ||
M: [email protected] and [email protected] | ||
S: Maintained | ||
|
||
HPET: ACPI hpet.c | ||
|
@@ -2652,6 +2652,19 @@ T: git kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6.git | |
T: cvs cvs.parisc-linux.org:/var/cvs/linux-2.6 | ||
S: Maintained | ||
|
||
PARAVIRT_OPS INTERFACE | ||
P: Jeremy Fitzhardinge | ||
M: [email protected] | ||
P: Chris Wright | ||
M: [email protected] | ||
P: Zachary Amsden | ||
M: [email protected] | ||
P: Rusty Russell | ||
M: [email protected] | ||
L: [email protected] | ||
L: [email protected] | ||
S: Supported | ||
|
||
PC87360 HARDWARE MONITORING DRIVER | ||
P: Jim Cromie | ||
M: [email protected] | ||
|
@@ -3876,6 +3889,15 @@ M: [email protected] | |
L: [email protected] | ||
S: Maintained | ||
|
||
XEN HYPERVISOR INTERFACE | ||
P: Jeremy Fitzhardinge | ||
M: [email protected] | ||
P: Chris Wright | ||
M: [email protected] | ||
L: [email protected] | ||
L: [email protected] | ||
S: Supported | ||
|
||
XFS FILESYSTEM | ||
P: Silicon Graphics Inc | ||
P: Tim Shimmin, David Chatterton | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.