On 04/19/2013 05:49 PM, Jiří Zárevúcky wrote:
>> have you tried tester pingpong?
>> it should give an idea about ipc perf limits.
>>
>
> 6490 rt/s
The pingpong test doesn't create a new fibril for each received IPC
message, whereas notification handling does. Is this necessary? Why
don't we have just one fibril handling all notfications just like there
is a single fibril handling messages from a client? This would reduce
the (unnecessary) overhead of creating/destroying a fibril for each
message without any drawback I can think of (the async framework doesn't
do any routing for notifications anyway).
So the notification handler fibril/function might look like this
(compare with connection handler function):
void handle_notification(void) {
loop {
callid = async_get_notification(&call);
somehow_handle_the_notification(callid, call);
}
}
Martin Sucha
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
