linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: raz ben yehuda <razb@bitband.com>
To: lenb@kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Subject: [PATCH 1/2] linux-acpi: sos documentation
Date: Tue, 14 Oct 2008 01:38:13 +0200	[thread overview]
Message-ID: <1223941094.5437.17.camel@raz> (raw)

From: Raz Ben Yehuda <razb@bitband.com>

Signed-off-by: Raz Ben Yehuda <razb@bitband.com>
---

diff -urpN linux-2.6.27/Documentation/SOS.txt linux-2.6.27-dbg/Documentation/SOS.txt
--- linux-2.6.27/Documentation/SOS.txt	1970-01-01 02:00:00.000000000 +0200
+++ linux-2.6.27-dbg/Documentation/SOS.txt	2008-10-14 00:29:32.000000000 +0200
@@ -0,0 +1,14 @@
+				SOS
+
+SOS is a service oriented scheduler. SOS is a method of relating one or more
+distinct services to a processor.In other words, a core(s) is assigned to
+a chore, not a chore to a core.
+Technically speaking, by virtually removing a processor from the operating
+system, using Linux ACPI facility one can bind processors to services.
+SOS management and control is done by sosctl.
+To fully understand what is SOS, when should it be used it and for which
+puprose,please refer to http://sos-linux.cvs.sourceforge.net/sos-linux/sos/Documentation/.
+
+Author: Raz Ben Yehuda
+Date: 2/08/2008
+Open University Israel.Computer Sciences Department. MSC.


             reply	other threads:[~2008-10-13 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 23:38 raz ben yehuda [this message]
2008-10-17 10:18 ` Subject: [PATCH 1/2] linux-acpi: sos documentation Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2008-10-18  1:37 raz ben yehuda
2008-10-18 18:05 ` Pavel Machek
2008-09-15 11:48 raz ben yehuda

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=1223941094.5437.17.camel@raz \
    --to=razb@bitband.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).