New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce event dependencies #269

Open
rsmmr opened this Issue Feb 7, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@rsmmr
Copy link
Member

rsmmr commented Feb 7, 2019

As a prerequisite for asynchronous, or parallel, event execution, develop a way to express serialization constraints between event handlers, plus an event scheduler that takes these into account. There's prior work on how this could look like.

From an email thread on bro-dev

Subject:  [Bro-Dev] 'async' update and proposal

I think one
possible solution has been floating around for a while already: event
*scopes* that express serialization requirements in terms of shared
context. Most common example: serialize all events that are triggered
by the same connection. Originally this came up in the context of
running event handlers concurrently. I believe it would solve this
problem here too: when a function suspends, halt all handlers that
depend on the same context (e.g., same connection).
[...]
In a concurrent
prototype many years ago we instead used a hardcoded set of choices
based on the underlying connection triggering the event (5-tuple, host
pair, src IP, dst IP). So you'd write (iirc):

    event protocol_event_1(c: connection ...) &scope = connection
[... or/and ...]
   event protocol_event_1(c: connection ...) &context = { return c$id; } { ... }

Also see ��http://www.icir.org/robin/papers/ccs14-concurrency.pdf

@rsmmr rsmmr added the Project label Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment