* [PATCH] [RFC] memory.txt: remove stray information
@ 2012-09-18 21:42 Jiri Kosina
2012-09-18 21:50 ` Andi Kleen
0 siblings, 1 reply; 2+ messages in thread
From: Jiri Kosina @ 2012-09-18 21:42 UTC (permalink / raw)
To: Andi Kleen, Andrew Morton; +Cc: linux-kernel
Andi removed some outedated documentation from Documentation/memory.txt
back in 2009 by 3b2b9a875dd ("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 <jkosina@suse.cz>
---
Documentation/memory.txt | 33 ---------------------------------
1 files changed, 0 insertions(+), 33 deletions(-)
delete mode 100644 Documentation/memory.txt
diff --git a/Documentation/memory.txt b/Documentation/memory.txt
deleted file mode 100644
index 802efe5..0000000
--- a/Documentation/memory.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-There are several classic problems related to memory on Linux
-systems.
-
- 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
- motherboard.
-
-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.
-Try:
-
- * Reducing memory settings in the BIOS to the most conservative
- timings.
-
- * 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.
--
Jiri Kosina
SUSE Labs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] [RFC] memory.txt: remove stray information
2012-09-18 21:42 [PATCH] [RFC] memory.txt: remove stray information Jiri Kosina
@ 2012-09-18 21:50 ` Andi Kleen
0 siblings, 0 replies; 2+ messages in thread
From: Andi Kleen @ 2012-09-18 21:50 UTC (permalink / raw)
To: Jiri Kosina; +Cc: Andrew Morton, linux-kernel
> It seems to me like we are not losing anything by completely removing the
> file now.
The stuff at the end still seems useful, down from
"There are other memory problems which Linux cannot deal with...."
The rest could go I agree.
-Andi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-09-18 21:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-18 21:42 [PATCH] [RFC] memory.txt: remove stray information Jiri Kosina
2012-09-18 21:50 ` Andi Kleen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome