This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
wiki:todos:handle_hyperthreading_setup_in_jobs [2014/12/12 10:32] – Page moved from wiki:handle_hyperthreading_setup_in_jobs to wiki:todos:handle_hyperthreading_setup_in_jobs neyron | wiki:todos:handle_hyperthreading_setup_in_jobs [2015/05/26 15:07] – neyron | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | The idea is to allow the cpuset field in the database to store the id or many threads, e.g. 1+8 for thread 1 and thread 8. | + | |
+ | ====== First way ====== | ||
+ | |||
+ | The idea is to allow the cpuset field in the database to store the id or many threads, e.g. 1,8 for thread 1 and thread 8. | ||
As a result the cpuset field in OAR database must be converted from Int to Varchar. | As a result the cpuset field in OAR database must be converted from Int to Varchar. | ||
This implies a database schema upgrade. | This implies a database schema upgrade. | ||
Line 5: | Line 8: | ||
We have to check that code that changes or accesses the cpuset field will not break. | We have to check that code that changes or accesses the cpuset field will not break. | ||
- | Also the job resource manager will have to make use of the cpuset field correctly. | + | Also the job resource manager will have to make use of the cpuset field correctly. |
+ | |||
+ | |||
+ | **This is implemented in versions >= 2.5.4.** | ||
+ | |||
+ | ====== Second way ====== | ||
+ | |||
+ | Generally when a job wants to use Hyperthreading CPU feature it means that it can/must run on a whole computing node. | ||
+ | |||
+ | So it could be useful to have a job type " | ||
+ | |||
+ | Is someone interested by this feature??? | ||
+ | |||
+ |