From: Evgeniy Polyakov <[EMAIL PROTECTED]>
Date: Sat, 20 May 2006 19:52:02 +0400
> While developing first apporoach I've found that input TCP processing
> sometimes refers to dst_entry which can only be obtained through the input
> routing code. You can find appropriate changes in attached increm
The more I think about TCP processing in netchannels, the more I get
close to the following ideas:
* map netchannel to socket.
* implement own TCP (receiving for now) state machine.
So I would like to ask people, what do we want for netchannels
* existing Linux TCP stack
* fairly simple mi
This updates brings new features to the following supported:
* unified cache to store netchannels (IPv4 and stub for fied cache
to store netchannels (IPv4 and stub for IPv6 hashes, TCP and UDP)
* skb queueing mechanism
* netchannel creation/removing/reading commands
* netchannel's callback to all
