From: Peter Zijlstra <peterz@infradead.org>
To: "Jan H. Schönherr" <schnhrr@cs.tu-berlin.de>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Separate group-scheduling code more clearly
Date: Fri, 15 Jul 2011 12:14:16 +0200 [thread overview]
Message-ID: <1310724856.2586.298.camel@twins> (raw)
In-Reply-To: <1310661163-16606-1-git-send-email-schnhrr@cs.tu-berlin.de>
On Thu, 2011-07-14 at 18:32 +0200, Jan H. Schönherr wrote:
>
> I get your point, then what about doing it the other way round?
> The patch below should be more to your liking.
Yes, Thanks!
> One could do something similar with sched_init() to get rid of
> some #ifdefs, i. e. separating code based on features instead
> of handling all features intermixed. Not sure whether it is
> worth the effort, though...
I'll try and remember next time someone needs to touch that code ;-)
> PS: This time with an extra From line, so that your tools hopefully
> work without any problems. :)
They do, again thanks!
next prev parent reply other threads:[~2011-07-15 10:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310580816-10861-1-git-send-email-schnhrr@cs.tu-berlin.de>
2011-07-13 18:13 ` [PATCH 6/6] sched: Do not attempt to destroy uninitialized rt_bandwidth Jan H. Schönherr
2011-07-21 18:30 ` [tip:sched/core] " tip-bot for Bianca Lutz
[not found] ` <1310580816-10861-6-git-send-email-schnhrr@cs.tu-berlin.de>
2011-07-13 20:44 ` [PATCH 5/6] sched: Use leaf_cfs_rqs in load_balance_fair() Peter Zijlstra
2011-07-14 16:46 ` Jan Schönherr
[not found] ` <1310580816-10861-4-git-send-email-schnhrr@cs.tu-berlin.de>
2011-07-13 20:47 ` [PATCH 3/6] sched: Avoid redundant initialization of runqueues Peter Zijlstra
[not found] ` <1310661163-16606-1-git-send-email-schnhrr@cs.tu-berlin.de>
2011-07-15 10:14 ` Peter Zijlstra [this message]
[not found] ` <1310580816-10861-2-git-send-email-schnhrr@cs.tu-berlin.de>
2011-07-13 20:51 ` [PATCH 1/6] sched: Fix (harmless) typo 'CONFG_FAIR_GROUP_SCHED' Peter Zijlstra
2011-07-13 22:07 ` Jiri Kosina
2011-07-13 22:12 ` Peter Zijlstra
2011-07-13 22:25 ` Jiri Kosina
2011-07-13 22:37 ` Peter Zijlstra
2011-07-13 22:48 ` Jiri Kosina
2011-07-14 16:45 ` Jan Schönherr
2011-07-13 22:35 ` Jesper Juhl
2011-07-13 22:44 ` Peter Zijlstra
2011-07-13 23:03 ` Jesper Juhl
2011-07-13 23:18 ` Peter Zijlstra
2011-07-13 23:43 ` Jesper Juhl
2011-07-14 8:53 ` Alan Cox
2011-07-14 12:50 ` Peter Zijlstra
2011-07-14 13:23 ` Alan Cox
2011-07-21 18:29 ` [tip:sched/core] " tip-bot for Jan Schoenherr
2011-07-13 20:58 ` [PATCH 0/6] Small scheduling cleanups 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=1310724856.2586.298.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schnhrr@cs.tu-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.