Re: [RFC] cpuset: Explicit dynamic sched domain cpuset flag

[Paul Jackson]

Dinakar,

Where do we stand on this patch?

Last I knew, as of a week ago:

  * I had (still have) a patch in *-mm to nuke the old connection
    between the cpu_exclusive flag and sched domain partitioning:
	cpuset-remove-sched-domain-hooks-from-cpusets.patch
  * and you have this patch posted on lkml, with some non-trivial
    comments from myself, to provide a new 'sched_domain' per-cpuset
    flag to control sched domain partitioning.

Ideally, we'd agree on this new 'sched_domain' (or whatever we call it)
flag, so that my patch to remove the old hooks could travel to 2.6.20
along with this present patch to provide new and improved hooks.

However ... I need to focus on some other stuff for roughly four
weeks, so can't focus on pushing this effort along right now.

My guess is that I will end up asking Andrew to hold the above
named "remove ... hooks" patch in *-mm until you and I get our
act together on the replacement, which most likely will mean he
holds it until we start work on what will become 2.6.21.

Do you see any better choices?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@xxxxxxx> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/