Hi,
> > What do you think if you make cpusets for sched domain be able to
> > have their siblings, which have the same attribute and share
> > their resources between them.
>
> I do not understand this question. I guess "cpusets for sched
> domains" means "cpusets whose 'cpu_exclusive' attribute is
> marked true, but which have no child cpusets so marked."
Yes.
> But even that guess I am unsure of, and the rest of the sentence
> "which have the same ..." I don't even have a guess what means.
Sorry for the poor explanation.
I just thought that it wouldn't be bad to allow "each cpuset whose
cpu_exclusive attribute is mark true" to have its clones like the
figure below. In this case, cpu-2 and cpu-3 will be used exclusively
for the clones --- CPUSET 1, 2, and 3 ---.
I guess it seems very similar to one of your ideas except for reusing
cpu_exclusive flag. Do you think reusing the flag is good idea?
+-------------------+----------------+----------------+
| | | |
CPUSET 0 CPUSET 1 CPUSET 2 CPUSET 3
sched domain A sched domain B sched domain B sched domain B
cpus: 0, 1 cpus: 2, 3 cpus: 2, 3 cpus: 2, 3
cpu_exclusive cpu_exclusive cpu_exclusive cpu_exclusive
meter_cpu meter_cpu meter_cpu
<------should we call it resouce domain?------>
Thanks,
Hirokazu Takahashi.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |