From: Ingo Molnar <mingo@elte.hu>
To: Martin Steigerwald <ms@teamix.de>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] CFS scheduler: documentation about scheduling policies
Date: Tue, 23 Sep 2008 11:11:59 +0200 [thread overview]
Message-ID: <20080923091159.GE31189@elte.hu> (raw)
In-Reply-To: <200809231101.41624.ms@teamix.de>
* Martin Steigerwald <ms@teamix.de> wrote:
> The documentation about the CFS scheduler is scarse when it comes to
> scheduling policies. This patch adds a chapter about the scheduling policies
> it supports. Peter Zijlstra provided most of the information for it in
>
> http://marc.info/?l=linux-kernel&m=122210038326356&w=2
>
> This patch is based on 2.6.27-rc7.
>
> Signed-off-by: Martin Steigerwald <ms@teamix.de>
looks good to me - but could you please do the patch against the latest
scheduler tree, which has already updated this file (and which made your
patch not apply cleanly):
http://people.redhat.com/mingo/tip.git/README
also:
> --- sched-design-CFS.txt-2.6.27-rc7 2008-07-13 23:51:29.000000000 +0200
> +++ sched-design-CFS.txt 2008-09-23 10:33:01.107393509 +0200
please use -p1 to create patches - or since you've just set up the
tip/master tracking, do something like:
<modify Documentation/scheduler/sched-design-CFS.txt>
git-commit Documentation/scheduler/sched-design-CFS.txt
<add commit log>
and then export the commit you just created for use in emailing, via:
git log --pretty=email --stat -1 -p > mail.txt
Ingo
next prev parent reply other threads:[~2008-09-23 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 9:01 [PATCH] CFS scheduler: documentation about scheduling policies Martin Steigerwald
2008-09-23 9:11 ` Ingo Molnar [this message]
2008-09-23 9:53 ` Martin Steigerwald
2008-09-23 10:14 ` Ingo Molnar
2008-09-23 11:48 ` Martin Steigerwald
2008-09-23 11:50 ` Ingo Molnar
2008-09-23 12:01 ` Martin Steigerwald
2008-09-23 12:07 ` Ingo Molnar
2008-09-23 12:10 ` Peter Zijlstra
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=20080923091159.GE31189@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@teamix.de \
/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