Re: [patch 00/11] ANNOUNCE: "Syslets", generic asynchronous systemcall support

[Davide Libenzi]

On Tue, 13 Feb 2007, Ingo Molnar wrote:

> As it might be obvious to some of you, the syslet subsystem takes many 
> ideas and experience from my Tux in-kernel webserver :) The syslet code 
> originates from a heavy rewrite of the Tux-atom and the Tux-cachemiss 
> infrastructure.
> 
> Open issues:
> 
>  - the 'TID' of the 'head' thread currently varies depending on which 
>    thread is running the user-space context.
> 
>  - signal support is not fully thought through - probably the head 
>    should be getting all of them - the cachemiss threads are not really 
>    interested in executing signal handlers.
> 
>  - sys_fork() and sys_async_exec() should be filtered out from the 
>    syscalls that are allowed - first one only makes sense with ptregs, 
>    second one is a nice kernel recursion thing :) I didnt want to 
>    duplicate the sys_call_table though - maybe others have a better 
>    idea.

If this is going to be a generic AIO subsystem:

- Cancellation of peding request



- Davide


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/