On Tue, Apr 19, 2005 at 08:26:39AM -0700, Paul Jackson wrote: > * Your understanding of "cpu_exclusive" is not the same as mine.
Sorry for creating confusion by what I said earlier, I do understand exactly what cpu_exclusive means. Its just that when I started working on this (a long time ago) I had a different notion and that is what I was referring to, I probably should never have brought that up > > > Since isolated cpusets are trying to partition the system, this > > can be restricted to only the first level of cpusets. > > I do not think such a restriction is a good idea. For example, lets say > our 8 CPU system has the following cpusets: > And my current implementation has no such restriction, I was only suggesting that to simplify the code. > > > Also I think we can add further restrictions in terms not being able > > to change (add/remove) cpus within a isolated cpuset. > > My approach agrees on this restriction. Earlier I wrote: > > Also note that adding or removing a cpu from a cpuset that has > > its domain_cpu_current flag set true must fail, and similarly > > for domain_mem_current. > > This restriction is required in my approach because the CPUs in the > domain_cpu_current cpusets (the isolated CPUs, in your terms) form a > partition (disjoint cover) of the CPUs in the system, which property > would be violated immediately if any CPU were added or removed from any > cpuset defining the partition. See my other note explaining how things work currently. I do feel that this restriction is not good -Dinakar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/