On Thu, Feb 09, 2006 at 04:56:11PM +0300, Evgeniy Polyakov wrote:
> Hello.
>
> I'm pleased to announce following projects:
>
> 1/2 - Kevent subsystem.
> This subsystem incorporates several AIO/kqueue design notes and ideas.
> Kevent can be used both for edge and level notifications. It supports
> socket notifications (accept and receiving), inode notifications
> (create/remove), generic poll()/select() notifications, timer
> notifications and network AIO notifications.
What is the justification behind adding yet another notification system?
We already have AIO, epoll, traditional select/poll. This seems like a lot
of new code for no additional functionality.
> 2/2 - Network asynchronous IO. Receiving (TCP) support.
> Network AIO is based on kevent and works as usual kevent storage on top
> of it. It allows to receive data directly into userspace pages
> asynchronously from socket's receiving queue from softirq context.
Is there any reason for not using the existing aio read method?
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <[EMAIL PROTECTED]>.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
