Messages in this thread | | | From | "Perez-Gonzalez, Inaky" <> | Subject | RE: 2.6 must-fix list, v2 | Date | Tue, 13 May 2003 19:05:41 -0700 |
| |
> From: Shaheed R. Haque [mailto:srhaque@iee.org] > > Quoting Andrew Morton <akpm@digeo.com>: > > > "Shaheed R. Haque" <srhaque@iee.org> wrote: > > > > > > - Add ability to restrict the the default CPU affinity mask so that > > > sys_setaffinity() can be used to implement exclusive access to a CPU. > > > > Why is this useful? > > Because it allows one to dedicate a CPU to a process. For example, lets say you > have a quad processor,and want to run joe-random stuff on CPU 0, but a > specialised program on CPUs 1, 2, 3 that does not want to compete with > joe-random stuff.
Real time applications can also benefit from this; if I can get all the random stuff out of the way so that I know the important, timing-sensitive thingie in CPU1 will always get it, bonus points! ...
Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own (and my fault) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |