Re: [LARTC] tc feature request/bounty (fwd)
> for something like that to work, you need a lot of programming and > testing in different situations. > > Sharing traffic shaping across different boxes can become very > complicated if you want to do it right, I don't think you can find > experts willing to program and test everything, setup test networks etc. > for 300$. Thanks to jamal's latest tc action patch, and some perl duct tape (essentially polling the load per index, and modifying the "capacity" based on incoming announcements), I've been able to do what I wanted. :_) -alex ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] tc feature request/bounty (fwd)
Hi, for something like that to work, you need a lot of programming and testing in different situations. Sharing traffic shaping across different boxes can become very complicated if you want to do it right, I don't think you can find experts willing to program and test everything, setup test networks etc. for 300$. Good luck, Jeroen. On Mon, 12 Apr 2004 17:49:00 -0400 (EDT) [EMAIL PROTECTED] wrote: > Currently, linux tc has very useful concept of a 'index' for a given > policy. However, I need to have policers on multiple hosts to share the > same index (and thus, know and police the aggregate traffic across a set > of routers). > > I'd like to be able to share tc policers across a set of boxes. > Unfortunately, I'm not knowledgeable enough myself to implement that, but > I can throw some money at the pool and hope someone picks it up. ;) > > Proposed design: > > Userland daemon that polls kernel tc structure every X milliseconds and > broadcasts current bps rate (assuming we are using ewma) to a set of IP > addresses. Configuration would have list of indices and list of IP > addresses these indices are broadcast to. > > Kernel changes: Add netlink interface to look up/modify (by "injecting" > traffic) policer's structures (interface to tcf_police_lookup and > tcf_police_dump). > > Adding external traffic to policer structures is somewhat tricky, but I'm > sure it is possible. At this point, I only care about EWMA, which isn't > all that hard. > > Budget and bounty: 300$ > > Any takes? > > -alex > > > > > ___ > LARTC mailing list / [EMAIL PROTECTED] > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
[LARTC] tc feature request/bounty (fwd)
Currently, linux tc has very useful concept of a 'index' for a given policy. However, I need to have policers on multiple hosts to share the same index (and thus, know and police the aggregate traffic across a set of routers). I'd like to be able to share tc policers across a set of boxes. Unfortunately, I'm not knowledgeable enough myself to implement that, but I can throw some money at the pool and hope someone picks it up. ;) Proposed design: Userland daemon that polls kernel tc structure every X milliseconds and broadcasts current bps rate (assuming we are using ewma) to a set of IP addresses. Configuration would have list of indices and list of IP addresses these indices are broadcast to. Kernel changes: Add netlink interface to look up/modify (by "injecting" traffic) policer's structures (interface to tcf_police_lookup and tcf_police_dump). Adding external traffic to policer structures is somewhat tricky, but I'm sure it is possible. At this point, I only care about EWMA, which isn't all that hard. Budget and bounty: 300$ Any takes? -alex ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
