diff options
author | Vito Caputo <vcaputo@pengaru.com> | 2023-06-05 17:02:49 -0700 |
---|---|---|
committer | Vito Caputo <vcaputo@pengaru.com> | 2023-06-05 17:02:49 -0700 |
commit | c5597fa6d5e4b6f0f79a54b93b0f405b979beb81 (patch) | |
tree | 88c22d56597c39387a7e11a27543a9d2a1275dba /src/modules/checkers | |
parent | 9c3a5bad857ac5ee8584e96ee66c2e337efa55c0 (diff) |
til: introduce til_module_create_contexts() variant
checkers::fill_module is presently implemented via creating
n_cpus identical module contexts, each having n_cpus=1.
Establishing a set of cloned per-cpu contexts, allowing threaded
rendering using any fill_module, regardless of if that module
internally implements threaded rendering.
This works fine, but creates some awkwardness for a future where
contexts are registered and discoverable within the stream at
their respective setup's path. In the checkers::fill_module
case, there would be n_cpus contexts at the same path since they
share the same til_setup_t. Those need to be dealt with
gracefully, ideally making the clones available to another
potentially clone-needing module (imagine a checkers::fill_module
transitionining to another checkers::fill_module situation, where
the transitioned-to fill_module refers to the context by path, it
should get all the contexts out of the stream as-is)
In this commit I'm adding a more formalized method of creating
multiple contexts from the same set of parameters, in preparation
for a future where module contexts get registered on the stream
at their til_setup_t.path. By putting the cloned creates behind
the til API it should at least be relatively trivial to get the
on-stream context registration to capture the multiple contexts.
Diffstat (limited to 'src/modules/checkers')
0 files changed, 0 insertions, 0 deletions