A few days ago, Nick wrote:
> Well the scheduler simply can't handle it, so it is not so much a
> matter of pushing - you simply can't use partitioned domains and
> meaningfully have a cpuset above them.
And I (pj) replied:
> Translating that into cpuset-speak, I think what you mean is ...
I then went on to ask some questions. I haven't seen a reply.
I probably wrote too many words, and you had more pressing matters
to deal with. Which is fine.
Let's make this simpler.
Ignore cpusets -- let's just talk about a tasks cpus_allowed value,
and scheduler domains. Think of cpusets as just a strange way of
setting a tasks cpus_allowed value.
Question:
What happens if we have say two isolated scheduler domains
on a system, covering say two halves of the system, and
some task has its cpus_allowed set to allow _all_ CPUs?
What kind of pain does that cause? I'm hoping you will say that
the only pain it causes is that the task will only run on one
half of the system, even if the other half is idle. And that
so long as I don't mind that, it's no problem to do this.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.650.933.1373, 1.925.600.0401
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
