Messages in this thread | | | Subject | Re: 2.6 must-fix list, v2 | From | Steven Cole <> | Date | 13 May 2003 20:42:13 -0600 |
| |
On Tue, 2003-05-13 at 16:46, Shaheed R. Haque wrote: > 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. > > With sys_setaffinity(), one can set the affinity of the special program to > 0xe...but the default affinity for all the joe-random stuff is still 0xf (from > cpu_online_map)! Since its impractical to to modify every single joe-random > executable to set its affinity to 0x1, a way is needed to set the default. The > logical place is in init(), a.k.a. kernel/fork.c. > > I hope that make sense. > > Thanks, Shaheed >
Is this related or not to processor shielding used by RedHawk Linux? Here is a link to their page:
http://www.ccur.com/realtime/sys_rdhwklnx.html
I saw a presentation by these guys over a year ago. I'm not sure what they're up to now.
Steven
- 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/
| |