Displaying 3 results from an estimated 3 matches for "limit_thread_model".
2018 Jan 19
1
Re: [PATCH nbdkit filters-v3 3/7] Introduce filters.
...c.
> ---
> +
> +The filter’s C<.open> and C<.close> methods are called when a new
> +connection is opened or an old connection closed, and these have no
> +C<next> parameter because they cannot be short-circuited.
> +
Stale, given [1]
> +
> +=head2 C<.limit_thread_model>
> +
> + int (*limit_thread_model) (void);
Does this need to be a callback, or can it just be a compile-time value
the way plugins have a compile-time value? The backend has to have a
function, to find the most restrictive model in the chain, but I'm not
seeing how a filter would hav...
2018 Jan 19
0
[PATCH nbdkit filters-v3 3/7] Introduce filters.
...is unloaded from
+memory. Note that it's not guaranteed that C<.unload> will always be
+called (eg. the server might be killed or segfault), so you should try
+to make the filter as robust as possible by not requiring cleanup.
+See also L<nbdkit-plugin(3)/SHUTDOWN>.
+
+=head2 C<.limit_thread_model>
+
+ int (*limit_thread_model) (void);
+
+A filter may define this to make the plugin thread model more limited
+if, for some reason, the filter is unable to handle parallel requests.
+The callback, if defined, should return one of the
+C<NBDKIT_THREAD_MODEL_*> values (see L<nbdkit-plug...
2018 Jan 19
9
[PATCH nbdkit filters-v3 0/7] Introduce filters.
This is still tentative and needs a lot of work, but:
- partition filter works, supporting MBR & GPT
- prepare and finalize methods fixed
- open method can now be changed (allowing readonly flag to be modified)
- thread_model can be limited
I believe I made most of the changes which were previously suggested
in email. I think the only one I didn't was preventing inclusion of
both