netdev
[Top] [All Lists]

Re: RFC: PPP over X

To: jamal <hadi@xxxxxxxxxx>
Subject: Re: RFC: PPP over X
From: Michal Ostrowski <mostrows@xxxxxxxxxxxxxxxxx>
Date: Thu, 3 Feb 2000 16:35:19 -0500 (EST)
Cc: Mitchell Blank Jr <mitch@xxxxxxxxxx>, Michal Ostrowski <mostrows@xxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, axboe@xxxxxxx, Mark Spencer <markster@xxxxxxxxx>, Andi Kleen <ak@xxxxxxx>, Marc Boucher <marc@xxxxxxx>, paulus@xxxxxxxxxxxxx, Ben LaHaise <bcrl@xxxxxxxxxx>
In-reply-to: <Pine.GSO.4.20.0002031608140.25544-100000@shell.cyberus.ca>
References: <20000203111517.I72648@sfgoth.com> <Pine.GSO.4.20.0002031608140.25544-100000@shell.cyberus.ca>
Sender: owner-netdev@xxxxxxxxxxx
jamal writes:
 > 
 > mitch> I agree, especially if you're running a PPPoE session server, where
 > mitch> you need hundreds of simultaneous sessions demuxed.
 > mitch>
 > 
 > You just need to be able to select and/or poll; you dont necessarily need
 > sockets for that

I think the bigger issue there is that in such a situation it may not
be feasible to maintain a unique character device for each connection.
If you've got connections going up and down constantly it could be a
real hassle to try to match and bind them to character devices.

Socket's are ideal for this kind of thing since you don't need to
translate from the network-level naming (stuff that can be done with a
sockaddr) and character device naming in the file system.  Since any
sort of PPPoX code must be able to keep track of multiple connections
using an addressing/naming scheme unique to "X", using sockets with
an appropriately defined sockaddr derivative appears to be the natural
thing to do.

Michal Ostrowski
mostrows@xxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>