> David wrote: > > Just thinking it makes mroe sense to have 2 that are optimised... > > For me, it's first one more driver code source to maintain, and > many duplicate code to handling the basic driver kernel API. > Please, no. > > > Yeah, but when you call /dev/net/stack for a socket that's OK and > > not > > strange at all :) > > Okay, what about calling it /dev/net/stocket? > Or /dev/net/sacket ? > ;-) Why not just use ports? Spawn a kernel thread that watches for updates like this. Simple, direct communication, and no published entry point. -Nathan -- Fortune Cookie Says: "If you have to hate, hate gently"