On Thursday 21 December 2006 17:36, Evgeniy Polyakov wrote:
> Network channel [1] is peer-to-peer protocol agnostic communication channel
> between hardware and userspace. It uses unified cache to store it's
> channels, allows to allocate buffers for data from userspace mapped area
> or from other
correct me
if I'm wrong):
1. Overflow.
2. Handle multiple kernel event that only needs one user event. I.e. multiple
packet arriving at the same socket. The user should only see one IN event at
the time he is ready to handle it.
In an earlier post I suggested a scheme that solv
On Thursday 05 October 2006 16:15, Evgeniy Polyakov wrote:
> On Thu, Oct 05, 2006 at 04:01:19PM +0200, Hans Henrik Happe
([EMAIL PROTECTED]) wrote:
> > > And what happens when there are 3 empty at the beginning and \we need to
> > > put there 4 ready events?
> >
>
etails with indexing and wakeup notification that I have left
out, but I hope my idea is clear. I could give a more detailed description if
requested. Also, I'm a user-level programmer so I might not get the whole
picture.
Hans Henrik Happe
-
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
On Saturday 29 July 2006 18:18, Ulrich Drepper wrote:
> Evgeniy Polyakov wrote:
> > Btw, why do we want mapped ring of ready events?
> > If user requestd some event, he definitely wants to get them back when
> > they are ready, and not to check and then get them?
> > Could you please explain more o
On Thursday 08 June 2006 19:15, you wrote:
> After some enhancements made for netchannel subsystem I'm pleased to
> announce, that netchannel subsystem outperforms existing layered design
> both in CPU usage and network speed.
>
> Well, after such pretentious introduction I want to cool things dow
