[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.98.0706111146220.14121@woody.linux-foundation.org>
Date: Mon, 11 Jun 2007 11:48:00 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
cc: Ingo Molnar <mingo@...e.hu>, Nick Piggin <nickpiggin@...oo.com.au>,
efault@....de, kernel@...ivas.org, containers@...ts.osdl.org,
ckrm-tech@...ts.sourceforge.net, akpm@...ux-foundation.org,
pwil3058@...pond.net.au, tingy@...umass.edu, tong.n.li@...el.com,
wli@...omorphy.com, linux-kernel@...r.kernel.org,
dmitry.adamushko@...il.com, balbir@...ibm.com
Subject: Re: [RFC][PATCH 1/6] Introduce struct sched_entity and struct lrq
On Mon, 11 Jun 2007, Srivatsa Vaddagiri wrote:
>
> struct sched_entity
> stores essential attributes/execution-history used by CFS core
> to drive fairness between 'schedulable entities' (tasks, users etc)
Wouldn't this be sensible to integrate into CFS _regardless_ of anything
else?
Especially with the alleged "pluggable" scheduler model, one of the things
lacking in any pluggability is the fact that the core thread data
structures are anythign but pluggable. This patch makes it no more so, but
at least it abstracts out the fields that are used by the scheduler, and
would seem to be a nice cleanup. No?
Linus
-
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