Mitchell Blank Jr writes:
> > Serving up connections on such a scale brings up some issues. Most
> > importantly, there should be a single process which negotiates all
> > incoming connections.
>
> That's true - ideally I'd like to see pppd look more like apache.
> Most of the gloabal varaiables could move to a "struct atm_instance"
> and each one would have its own ppp options, plugins, etc.
> Ideally there would be some way to add/delete/tweek these
> connections on a running pppd (so you could have a nice little
> GNOME configuration dialog giving you instant-gratification
> changes)
I won't pretend to be an expert on pppd, but I think you'd want to
replace "/dev/ppp" with something like a netlink socket. Using a
socket would allow you to mux/demux data in a way that you can't do
with a character device.
>
> I think this would be a really great approach for people
> running terminal-servers or PPPo{E,ATM} concentrators using
> linux. At some point the "thousands of pppd processes" model
> breaks down - it would be much cleaner just to have a single
> process that just needs to set a bunch of async-io signals
> on a bunch of {sockets,ttys} and watch /dev/ppp0.
>
Good point.
Michal Ostrowski
mostrows@xxxxxxxxxxxxxxxxx
|