Some config options are available for several components, such as tvmaot.num_threads, tvmrt.num_threads, mlif.num_threads, zephyr.num_threads,...
Defining them for every single component can be annoying, so Iw Ould like to make this more straightforward by allowing "wildcard" patters in the config options. Let me recommend 3 different approaches:
Regex-like: tvm[aot|rt].num_threads or similar should be possible, however I am not sure if this would be too complex.
*-only: *.num_threads would update the config of every component which has a config called num_threads. The only issue I have with this, is that * is a reserved YAM character, thus it needs to be escaped when used in environment.yml like this \*.num_threads: true or "*.num_threads": true
_.only: Using _.num_threads might be less straightforward than *.num_threads, however this does not need to be escaped when used in a YAML file.
Some config options are available for several components, such as
tvmaot.num_threads,tvmrt.num_threads,mlif.num_threads,zephyr.num_threads,...Defining them for every single component can be annoying, so Iw Ould like to make this more straightforward by allowing "wildcard" patters in the config options. Let me recommend 3 different approaches:
tvm[aot|rt].num_threadsor similar should be possible, however I am not sure if this would be too complex.*-only:*.num_threadswould update the config of every component which has a config callednum_threads. The only issue I have with this, is that*is a reserved YAM character, thus it needs to be escaped when used inenvironment.ymllike this\*.num_threads: trueor"*.num_threads": true_.only: Using_.num_threadsmight be less straightforward than*.num_threads, however this does not need to be escaped when used in a YAML file.What do you this @rafzi?