On Sat, 2007-05-26 at 00:18 +0200, Thomas Graf wrote:

This area is still work in progress but the basic idea is that
like in kernel context, the application defines its set of
commands and assigns message parsers for each command. 

Ok, but why? For when we get asynchronous events from the kernel?

For now,
the message parser is linked into the cache operations which
means that you have to "update" a cache in order to use this
feature. 

What's the cache good for to start with?

My current userland tool just send a message and expects back a
response. Obviously that's broken once we have events too, is that when
the message parsers come in?

johannes