From: raz ben yehuda <razb@bitband.com>
To: pavel@suse.cz
Cc: lkml <linux-kernel@vger.kernel.org>, linux-acpi@vger.kernel.org
Subject: RE: Subject: [PATCH 1/2] linux-acpi: sos documentation
Date: Sat, 18 Oct 2008 03:37:35 +0200 [thread overview]
Message-ID: <1224293855.3652.36.camel@raz> (raw)
First , I really really thank you for replying, This is not the first post I made for sos.
For some reason I did not get your reply.
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...
Do you mean diffstat ? I added diffstat at the sos-api patch. .
Are you referring to Documentation/Changes ? I am not sure I know what you mean.
> 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.
1. I posted to lkml as well as acpi. is this what you mean ?
2. At first, I posted a big text file , but I got zero replies so i thought that maybe people refrain from reading so much.
But I will fix it (I read SubmittingPatches).
>>Plus select some better acronym.
>> Pavel
How about ops ( offload-processor scheduler ) ? any other suggestions ? well.. I am bad at names.
raz
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-10-18 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 1:37 raz ben yehuda [this message]
2008-10-18 18:05 ` Subject: [PATCH 1/2] linux-acpi: sos documentation Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 23:38 raz ben yehuda
2008-10-17 10:18 ` 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=1224293855.3652.36.camel@raz \
--to=razb@bitband.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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