Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)

[chas williams]

In message <[e-mail]>,Werner Almesberger writes:
>Even with the route, the destination can remain "fixed".
>The VCC only makes sense in the context of the device, which
>is fully visible to the user. (It's different in the case of
>SVCs, but they're managed by a user space demon. Besides, if
>their device goes away, they die too.)

actually i think its a good idea to uncouple the atm
devices and the vcc.  while the vcc is useless w/o the
atm dev, there are quite a few resources tied to the vcc
(via sk side).  not having them seperate orignally led
to the 'nodev' atm device as a place to keep track of 
vcc that are going away.

once the atm device/vcc are uncoupled they can easily be
converted to a net device.  this keeps me from needing to
replicate the net device code (particularly the sysfs
stuff -- or so i hope).   netdevices already have a handy
register/unregister that works (and will keep working).
why would i want to duplicate the net device work?