.camel@xxxxxxxxxxxxxxxx> 2005-01-10 17:05 I started testing via the basic classifier but will do the cls_u32 changes soon and then remerge and do the final tests once all t
d they replaced it. Somehow they managed to break the trackpad and sungem. The trackpad works sometimes, sometimes not. The sungem needs now Today I wondered w
an up all the error paths, allow changing all pararmeters for those not supporting it yet and to add the action bits for tcindex, route, and rsvp. Finishing it
There are several instances of request_module beeing called while holding the rtnl semaphore in net/sched. A pratical problem with this is the teql scheduler which deadlocks when calling register_net
There are a couple of causes for this problem: 1) Abuse of the rtnl. It's being used for too many things. It's basically the networking system's BKL. If the locking were more granular then this shoul
I totally disagree. The use of rtnl for all networking configuration changes is a virtue of our current setup. All of these actions want to make sure devices don't disappear from underneath them whil
David S. Miller wrote: On Sat, 06 Nov 2004 10:35:45 +1100 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: 2) Hooking random net/sched requests into rtnetlink. By being an rtnetlink user you pay the p
* David S. Miller <20041109161126.376f755c.davem@xxxxxxxxxxxxx> 2004-11-09 16:11 Sounds reasonable for the sch_api.c and cls_api.c case but will get very nasty for act_api as you noted and any furthe
Thomas Graf wrote: Sounds reasonable for the sch_api.c and cls_api.c case but will get very nasty for act_api as you noted and any further sub layers that might be added in the future. (The classifie
I agree with that. However, my point is that the RTNL is used for a lot more than that. You could do that if the RTNL was exclusively used for protecting net_device. As it is it protects RTNETLINK an
* Patrick McHardy <41916A91.3080107@xxxxxxxxx> 2004-11-10 02:10 The action code might load modules in the middle of a classifier configuration and it will be very hard to reverse those changes. Right
Thomas Graf wrote: * Patrick McHardy <41916A91.3080107@xxxxxxxxx> 2004-11-10 02:10 Can you please show an example of a case where this is needed ? Just to help me understand. The action code might lo
* Patrick McHardy <41916F0B.5010809@xxxxxxxxx> 2004-11-10 02:29 I agree but this assumption is wrong, at least for u32. I agree that once this is true it would work perfectly fine, however I think it
Well it's only going to happen once for each module so that's no big deal. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://g
Thomas Graf wrote: * Patrick McHardy <41916F0B.5010809@xxxxxxxxx> 2004-11-10 02:29 Assuming all error-paths do proper cleanup, returning -EAGAIN should always result in the same configuration state a