Re: Hurdish TCP stack (was: updated proposal)

2008-04-01 Thread Joshua Stratton
Okay, I understand. I think part of this goes back to a question on the reason for enumeration on these sockets (tcp0, tcp1, etc.) if they aren't used directly in the socket interface for the developer. I assumed it was as a convenience for other programs that were monitoring the network. I agre

Re: Hurdish TCP stack (was: updated proposal)

2008-04-01 Thread Richard Braun
On Tue, Apr 01, 2008 at 08:07:23AM -0600, Joshua Stratton wrote: > > It's clearly a mistake to map the directory tree to the protocols stack. > > The TCP implementation is a global layer, it handles network interfaces > > internally and must not be bound to any interface (ask yourself how to > > im

Re: Hurdish TCP stack (was: updated proposal)

2008-04-01 Thread Joshua Stratton
> > > > I think this approach would fit nicely into the Hurd's translator > > architecture. However, I'm not sure if I like the directory structure > they > > use. I would think the network interface should be shown like > > > > /net/eth0/tcp/2 > > > > It might be worthwhile--but possible bad sty

Re: Hurdish TCP stack (was: updated proposal)

2008-04-01 Thread Richard Braun
On Mon, Mar 31, 2008 at 02:07:26PM -0600, Joshua Stratton wrote: > If anyone hasn't read up on how Plan9 runs their network stack, they have a > separate directory of each connection. An example in the paper is shown as > the following, > > # cd /net/tcp/2 <--- this is like the second TCP conne

Re: Hurdish TCP stack (was: updated proposal)

2008-03-31 Thread Joshua Stratton
If anyone hasn't read up on how Plan9 runs their network stack, they have a separate directory of each connection. An example in the paper is shown as the following, # cd /net/tcp/2 <--- this is like the second TCP connection # ls -l ctl data listen local remote status They use an interesting

Re: Hurdish TCP stack (was: updated proposal)

2008-03-31 Thread Joshua Stratton
Hey, I did some reading up on the Plan9 design for their network hierarchy. I think it's interesting. I wouldn't mind using it just so the layout would be more commonplace (for those who may have used Plan9). I also like the access to the interface statistics. Plan9, from what I've read, tries

Hurdish TCP stack (was: updated proposal)

2008-03-30 Thread olafBuddenhagen
Hi, On Sat, Mar 29, 2008 at 05:04:48PM +0100, Carl Fredrik Hammar wrote: > > /ip/eth0/tcp/ /ip/eth0/udp/ /ip/eth1/tcp/ /ip/eth1/udp/ /ip/lo/tcp/ > > /ip/lo/udp/ /ip/tcp/ /ip/udp/ [...] > Shouldn't it be /eth0/ip/tcp/? I.e. with internet protocol is layered > over ethernet. Indeed, the more I th