On Thu, Jan 10, 2013 at 6:09 PM, Bond wrote:
> On Thu, Jan 10, 2013 at 9:00 AM, Preeti U Murthy
> wrote:
> > d1's 'groups',both the sd0s.Here is
> > the next advantage.It needs information about the sched group alone and
> > will not bother about the individual cpus in it.it checks if
> > load(s
On Thu, Jan 10, 2013 at 9:00 AM, Preeti U Murthy
wrote:
> d1's 'groups',both the sd0s.Here is
> the next advantage.It needs information about the sched group alone and
> will not bother about the individual cpus in it.it checks if
> load(sd0[cpu2,cpu3]) > load(sd0[cpu0,cpu1])
> Only if this is tru
On 01/09/2013 01:33 PM, Bond wrote:
> The answer of the question that I want to know is
> why is a scheduling domain actually needed?
Scheduling domains and scheduler groups/cpu groups help to ease the
process of scheduling tasks like:
1.load balancing tasks across cpus.
2.choosing a cpu for a ne
On Wed, Jan 9, 2013 at 4:03 PM, Bond wrote:
> Hi,
> please see this question
>
> http://stackoverflow.com/questions/14229793/what-does-struct-sched-domain-stands-for-in-include-linux-sched-h-scheduling-do
>
> I checked following
> http://lwn.net/Articles/169277/ and following
> http://www.kernel.
