Hey Corey.
There are two discussions together here, and I'd like to pull them apart a bit. Recycle was originally created to provide the "revoke badges + cancel previous sends with those badges" use case. The operations for other typed caps were added for some kind of
consistency. The first question is whether anyone's using any of these additional operations. The second question is whether anyone uses the core "cancel waiting badged sends" bit.
If no-one's using the additional operations (and there's little reason to use them, except to save on a system call) we can specialise and simplify the implementation a lot. If in addition no-one is using the second part, we can drop the API feature entirely.
I'm in favour of dropping it entirely, and I have a user-level workaround which I can explain in more detail if you're interested [1].
So, long story, what were you planning on doing with badge cancellation in Robigalia?
Cheers,
Thomas.
1: OK, short version, a multi-user server can keep a spare thread around, revoke some badges, and then queue the thread in the endpoint as a sentinel, with a message saying "you may now reuse the revoked badges".
On 29/10/16 02:24, Corey Richardson wrote:
On 10/25/2016 11:54 PM, Adrian.Danis@data61.csiro.au wrote:
Whilst we do not use recycle we would like to first find out if anybody
in the community is using recycle, or has a strong argument for why they
would like it to stay. If this is you, please let us know, otherwise we
will continue with our plans for removal.
Robigalia doesn't and won't, except for the specific "revoke badges"
usecase. We definitely need that, but not anything else.
_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel