lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 23 Sep 2008 11:11:59 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Martin Steigerwald <ms@...mix.de>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH] CFS scheduler: documentation about scheduling policies


* Martin Steigerwald <ms@...mix.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@...mix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ