Re: [PATCH] set_cpus_allowed() for 2.4
Jeff Garzik (firstname.lastname@example.org)
Mon, 02 Dec 2002 12:24:49 -0500
Christoph Hellwig wrote:
> now that all commercial vendors ship a backport of Ingo's O(1) scheduler
> external projects like XFS have to track those projects in addition to the
> mainline kernel.
> Having the common new APIs available in mainline would be a very good thing
> for those projects. We already have a proper yield() in 2.4.20, but the
> set_cpus_allowed() API as used e.g. for kernelthreads bound to CPUs is
> still missing.
> Any chance you could apply Robert Love's patch to add it for 2.4.21? Note
> that it does not change any existing code but just adds that interface.
Adding to that, it is also used for backporting Ingo's workqueue stuff,
which is useful and completely separate from the O(1) scheduler.
I plan on using workqueues for moving some drivers' duties to process
context where it really belongs [which in turn fixes bugs].
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/