On Tue, 27 Nov 2007 14:57:26 +0100 Ariane Keller <[EMAIL PROTECTED]> wrote:
> I just wanted to ask whether there is a general interest in this patch. > If yes: great, how to proceed? > otherwise: please let me know why. > > Thanks! > > > > > Ariane Keller wrote: > > Hi Stephen > > > > Approximately a year ago we discussed an enhancement to netem, > > which we called "trace control for netem". > > > > We obtain the value for the packet delay, drop, duplication and > > corruption from a so called "trace file". The trace file may be obtained > > by monitoring network traffic and thus enables us to emulate "real > > world" network behavior. > > > > Traces can ether be generated individually (we supply a set of tools to > > do this) or can be downloaded from our homepage: http://tcn.hypert.net . > > > > Since our last submission on 2006-12-15 we did some code clean up and > > have created two new patches one against kernel 2.6.23.8 and one against > > iproute2-2.6.23. > > To refer to our discussion from last year please have a look at messages > > with subject "LARTC: trace control for netem". > > > > We are looking forward for any comments, suggestions and instructions to > > bring the trace enhancement to the kernel and to iproute2. > > > > Thanks, > > Ariane Still interested in this. I got part way through integrating it but had concerns about the API from the application to netem for getting the data. It seemed like there ought to be a better way to do it that could handle large data sets better, but never really got a good solution worked out (that is why I never said anything). The 2.6.23.8 patch seems to be unavailable right now. -- Stephen Hemminger <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
