From: <ffrederick@prov-liege.be>
To: <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.6.0-test6mm1] smp doc improved
Date: Sun, 5 Oct 2003 08:51:53 PDT [thread overview]
Message-ID: <S262801AbTJFGun/20031006065043Z+8586@vger.kernel.org> (raw)
Andrew,
Here's a patch to improve smp doc.
Could you apply ?
Regards,
Fabian
diff -Naur orig/Documentation/smp.txt edited/Documentation/smp.txt
--- orig/Documentation/smp.txt 2003-09-28 00:50:48.000000000 +0000
+++ edited/Documentation/smp.txt 2003-10-05 23:51:04.000000000 +0000
@@ -1,4 +1,14 @@
-To set up SMP
+Documentation for SMP (Symmetric Multi-Processing). Kernel version 2.6.0-test6
+Some improvements by Fabian Frederick <ffrederick@users.sourceforge.net> 2003
+
+===============================================================================
+
+Linux 2.2.X kernel series was the very beginning of multi-processor support.
+Here are some tips to manage SMP and to figure out it works properly.
+
+===============================================================================
+
+How to setup SMP:
Configure the kernel and answer Y to CONFIG_SMP.
@@ -20,3 +30,21 @@
If you are using some Compaq MP compliant machines you will need to set
the operating system in the BIOS settings to "Unixware" - don't ask me
why Compaqs don't work otherwise.
+
+===============================================================================
+
+How to know SMP is running properly:
+
+You can cat /proc/cpuinfo for instance.That will display each processor with all its properties.
+
+processor :0
+vendor_id
+....
+processor :1
+....
+
+For a simple status you can also cat /proc/stat where first entries display
+cpu statistics.First line titled 'cpu' is a grand total.'cpu0' 'cpu1' processor units.
+
+
+
___________________________________
reply other threads:[~2003-10-06 6:50 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=S262801AbTJFGun/20031006065043Z+8586@vger.kernel.org \
--to=ffrederick@prov-liege.be \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®