From: Dong Mo <montedong@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] New to codel-- how to run codel on a linux box?
Date: Thu, 5 Dec 2013 16:29:37 -0600 [thread overview]
Message-ID: <CAAUsAoRsbZVT0K1hykYTmKo88Ljjjw9hqF4RuSqDcrp+4ihg-A@mail.gmail.com> (raw)
In-Reply-To: <87ob4vau2z.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
I also found this to sample tcp latency performance:
https://code.google.com/p/paping/
<https://code.google.com/p/paping/>Does fq_codel's flow classification
supports external classifier filter? Say I only want to hash on dst port in
my case.
Thanks
Mo
2013/12/5 Toke Høiland-Jørgensen <toke@toke.dk>
> Dong Mo <montedong@gmail.com> writes:
>
> > What I am trying to do is measure the delay of packets of the same
> > flow experienced in A under different queuing policies (sfq or
> > fq_codel).
> >
> > Is there a simple way to do this?
>
> I'm currently in the early planning stages for having something like
> this incorporated into the netperf-wrapper [1] testing tool. In the
> meantime, you could look at either thrulay [2] (old and apparently
> abandoned, but may work in one of its variants) as a measurement tool,
> or tcpprobe [3] to output statistics that can (probably) tell you.
>
> -Toke
>
> [1] https://github.com/tohojo/netperf-wrapper
>
> [2] http://e2epi.internet2.edu/thrulay/
> http://thrulay-hd.sourceforge.net/
> http://thrulay-ng.sourceforge.net/
>
> [3]
> http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
>
[-- Attachment #2: Type: text/html, Size: 2109 bytes --]
next prev parent reply other threads:[~2013-12-05 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 5:04 Dong Mo
2013-11-23 10:23 ` Jonathan Morton
2013-11-23 14:43 ` Dave Taht
2013-12-05 19:36 ` Dong Mo
2013-12-05 19:49 ` Dong Mo
2013-12-05 20:06 ` Jonathan Morton
2013-12-05 20:21 ` Dong Mo
2013-12-05 21:03 ` Toke Høiland-Jørgensen
2013-12-05 22:29 ` Dong Mo [this message]
2013-12-05 23:25 ` Toke Høiland-Jørgensen
2013-12-05 23:28 ` Dong Mo
2013-12-05 23:43 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAUsAoRsbZVT0K1hykYTmKo88Ljjjw9hqF4RuSqDcrp+4ihg-A@mail.gmail.com \
--to=montedong@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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