On Tue, 2001-12-11 at 13:16, Tim Hockin wrote:
> Jason Baietto wrote:
> > support it in my "run" tool, though I fear that it would always be
> > functionally limited without /proc present.
> Adding /proc/ interfaces like cpus_allowed or similar is just gravy
> on top of pset, which I think is a good interface.
Sorry for the ambiguity. My comment was about the functionality of
the "run" tool itself being limited without /proc support.
Although I agree that ultimately "run" is gravy, our customers think
it's pretty tasty gravy :-) It's very convenient to write a shell
script to start up a complex application without having to reference
pids anywhere and without having to modify any of the programs in
the application to make them CPU affinity aware. Combined with run's
ability to tune scheduling parameters, you have a very simple but
powerful way to experiment with and tune application performance.
The run tool also allows you to quickly move processes around by
specifying lists of pids, process names, process groups or users,
but /proc is needed for anything more interesting than pids.
-- Jason Baietto firstname.lastname@example.org http://www.ccur.com/realtime/oss
- 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/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:23 EST