diff options
author | Vito Caputo <vcaputo@pengaru.com> | 2023-07-28 15:20:58 -0700 |
---|---|---|
committer | Vito Caputo <vcaputo@pengaru.com> | 2023-07-28 16:34:18 -0700 |
commit | 5221c25be67ee96a747c4e527436c0daa394a44e (patch) | |
tree | 88baa2f1310d0fe140e578009b44d012ba71dd91 /m4 | |
parent | ddb8c7e9ef62a699646745273b0e28324ddde455 (diff) |
til: introduce til_module_render_limited() variant
With the introduction of discoverable on-stream contexts, with
the intention of modules finding them at runtime for nested
rendering, relying exclusively on limiting n_cpus @
til_module_create_context() is no longer adequate.
When the nested rendering makes use of a context created
elsewhere, it can't make any assumptions about what its n_cpus
is, nor should it be attempting to change that value for its use.
So this variant just adds a max_cpus parameter for setting an
upper bound to whatever is found in the context's n_cpus.
The impetus for this is to fix the ref builtin, which you can
currently trick into deadlock by performing a nested threaded
render within a threaded render. What the ref module should be
doing is propagating its own context's n_cpus down as the upper
bound, via this new render variant.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions