|author||Jiri Kosina <firstname.lastname@example.org>||2012-10-08 16:33:25 -0700|
|committer||Linus Torvalds <email@example.com>||2012-10-09 16:22:57 +0900|
memory.txt: remove stray information
Andi removed some outedated documentation from Documentation/memory.txt back in 2009 by commit 3b2b9a875ddc ("Documentation/memory.txt: remove some very outdated recommendations"), but the resulting document is not in a nice shape either. It seems to me like we are not losing anything by completely removing the file now. Signed-off-by: Jiri Kosina <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'Documentation')
1 files changed, 0 insertions, 33 deletions
diff --git a/Documentation/memory.txt b/Documentation/memory.txt
deleted file mode 100644
@@ -1,33 +0,0 @@
-There are several classic problems related to memory on Linux
- 1) There are some motherboards that will not cache above
- a certain quantity of memory. If you have one of these
- motherboards, your system will be SLOWER, not faster
- as you add more memory. Consider exchanging your
-All of these problems can be addressed with the "mem=XXXM" boot option
-(where XXX is the size of RAM to use in megabytes).
-It can also tell Linux to use less memory than is actually installed.
-If you use "mem=" on a machine with PCI, consider using "memmap=" to avoid
-physical address space collisions.
-See the documentation of your boot loader (LILO, grub, loadlin, etc.) about
-how to pass options to the kernel.
-There are other memory problems which Linux cannot deal with. Random
-corruption of memory is usually a sign of serious hardware trouble.
- * Reducing memory settings in the BIOS to the most conservative
- * Adding a cooling fan.
- * Not overclocking your CPU.
- * Having the memory tested in a memory tester or exchanged
- with the vendor. Consider testing it with memtest86 yourself.
- * Exchanging your CPU, cache, or motherboard for one that works.