From: Ariane Keller <ariane.keller@tik.ee.ethz.ch>
To: Ben Greear <greearb@candelatech.com>
Cc: Ariane Keller <ariane.keller@tik.ee.ethz.ch>,
Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, Rainer Baumann <baumann@tik.ee.ethz.ch>
Subject: Re: [PATCH 0/2] netem: trace enhancement
Date: Sun, 23 Dec 2007 20:54:24 +0100 [thread overview]
Message-ID: <476EBCF0.3040507@ee.ethz.ch> (raw)
In-Reply-To: <4755D2EB.4000807@candelatech.com>
I have added the possibility to configure the number
of buffers used to store the trace data for packet delays.
The complete command to start netem with a trace file is:
tc qdisc add dev eth1 root netem trace path/to/trace/file.bin buf 3
loops 1 0
with buf: the number of buffers to be used
loops: how many times to loop through the tracefile
the last argument is optional and specifies whether the default is to
drop packets or 0-delay them.
The patches are available at:
http://www.tcn.hypert.net/tcn_kernel_2_6_23_confbuf
http://www.tcn.hypert.net/tcn_iproute2_2_6_23_confbuf
I'm looking forward for your comments!
Thanks!
Ariane
Ben Greear wrote:
> Ariane Keller wrote:
>
>> Yes, for short-term starvation it helps certainly.
>> But I'm still not convinced that it is really necessary to add more
>> buffers, because I'm not sure whether the bottleneck is really the
>> loading of data from user space to kernel space.
>> Some basic tests have shown that the kernel starts loosing packets at
>> approximately the same packet rate regardless whether we use netem, or
>> netem with the trace extension.
>> But if you have contrary experience I'm happy to add a parameter which
>> defines the number of buffers.
>
> I have no numbers, so if you think it works, then that is fine with me.
>
> If you actually run out of the trace buffers, do you just continue to
> run with the last settings? If so, that would keep up throughput
> even if you are out of trace buffers...
>
> What rates do you see, btw? (pps, bps).
>
> Thanks,
> Ben
>
--
Ariane Keller
Communication Systems Research Group, ETH Zurich
Web: http://www.csg.ethz.ch/people/arkeller
Office: ETZ G 60.1, Gloriastrasse 35, 8092 Zurich
next prev parent reply other threads:[~2007-12-23 19:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 22:11 [PATCH 0/2] netem: trace enhancement Ariane Keller
2007-11-27 13:57 ` Ariane Keller
2007-11-29 21:45 ` Stephen Hemminger
2007-11-29 22:03 ` Patrick McHardy
2007-11-30 16:25 ` Ariane Keller
2007-12-03 7:45 ` Patrick McHardy
2007-12-03 9:12 ` Ariane Keller
2007-12-03 17:35 ` Patrick McHardy
2007-12-03 18:29 ` Ben Greear
2007-12-04 14:45 ` Ariane Keller
2007-12-04 14:58 ` Patrick McHardy
2007-12-05 12:57 ` Ariane Keller
2007-12-05 13:05 ` Patrick McHardy
2007-12-10 14:32 ` Ariane Keller
2007-12-12 23:13 ` Stephen Hemminger
2007-12-04 17:40 ` Ben Greear
2007-12-04 17:54 ` Ariane Keller
2007-12-04 18:07 ` Ben Greear
2007-12-04 21:41 ` Ariane Keller
2007-12-04 22:21 ` Ben Greear
2007-12-05 6:12 ` Ariane Keller
2007-12-23 19:54 ` Ariane Keller [this message]
2007-12-23 19:54 ` [PATCH 0/2] netem: trace enhancement: kernel Ariane Keller
2007-12-28 16:08 ` Patrick McHardy
2007-12-28 21:02 ` Ariane Keller
2007-12-23 19:54 ` [PATCH 0/2] netem: trace enhancement: iproute Ariane Keller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476EBCF0.3040507@ee.ethz.ch \
--to=ariane.keller@tik.ee.ethz.ch \
--cc=baumann@tik.ee.ethz.ch \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).