From: Pavel Machek <pavel@suse.cz>
To: raz ben yehuda <razb@bitband.com>
Cc: lenb@kernel.org, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: Subject: [PATCH 1/2] linux-acpi: sos documentation
Date: Fri, 17 Oct 2008 12:18:44 +0200 [thread overview]
Message-ID: <20081017101844.GB10850@ucw.cz> (raw)
In-Reply-To: <1223941094.5437.17.camel@raz>
On Tue 2008-10-14 01:38:13, raz ben yehuda wrote:
> From: Raz Ben Yehuda <razb@bitband.com>
>
> Signed-off-by: Raz Ben Yehuda <razb@bitband.com>
> ---
No changelog, useful...
> 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/.
> +
I don't think this should be acpi specific... and you should provide
real doc, not pointer to web page.
Plus select some better acronym.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-17 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 23:38 raz ben yehuda
2008-10-17 10:18 ` Pavel Machek [this message]
2008-10-18 1:37 raz ben yehuda
2008-10-18 18:05 ` Pavel Machek
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=20081017101844.GB10850@ucw.cz \
--to=pavel@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=razb@bitband.com \
/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®