On Mon, Mar 31, 2008 at 9:23 PM, Joshua Stratton <
strattonbrazil@gmail.com> wrote:
I was on the irc channel talking about the feasibility using client-side memory buffers for a new network stack. Based on some feedback about difficulties of implementing this in the Hurd, I thought I would ask anyone if they thought this would be especially difficult--particularly Marcus and Neal.
Although I'm not sure, I've read Marcus implemented POSIX shared memory now, so I figured that would be the connected memory buffer the server would write to. If I understand it correctly (and I would love to get a better understanding of this), the network stack could make this memory block and assign this to the client (or the client would have ownership).
I was considering a domain socket, but supposedly this works much faster. Also, using shmctl the server could create resources assigned to the client such that the network stack itself wouldn't be responsible for the memory and it would be freed when the client died.
So is POSIX shared memory now functioning perfectly in the HURD? And would this mechanism function well for this client-side memory management for the new TCP/IP stack?
Josh