| commit | 62a7273db5a50c12b84157ea0c81b8669fd95367 | [log] [tgz] |
|---|---|---|
| author | Jens Axboe <jens.axboe@oracle.com> | Mon Dec 08 11:37:01 2008 +0100 |
| committer | Jens Axboe <jens.axboe@oracle.com> | Mon Dec 08 11:37:01 2008 +0100 |
| tree | ac2846e0ab14eedd36fb17f352f9da08364b95e7 | |
| parent | dbad30b097de39d355b3952a3bb6db9ccf9dd77f [diff] |
Allow ranges of CPUs in cpus_allowed option For a larger number of CPUs, it's a bit of a bother having to set each one individually. Plus, you typically want to bind to a range of CPUs, to keep the job core local (or whatever your preference). So extend cpus_allowed to take ranges of CPU numbers as well. Now you can do: cpus_allowed=0-7 and have your job confined to CPUs 0 through 7. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>