CoDel AQM discussions
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dong Mo <montedong@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] New to codel-- how to run codel on a linux box?
Date: Thu, 05 Dec 2013 23:25:40 +0000	[thread overview]
Message-ID: <87fvq6c22z.fsf@toke.dk> (raw)
In-Reply-To: <CAAUsAoRsbZVT0K1hykYTmKo88Ljjjw9hqF4RuSqDcrp+4ihg-A@mail.gmail.com> (Dong Mo's message of "Thu, 5 Dec 2013 16:29:37 -0600")

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

Dong Mo <montedong@gmail.com> writes:

> I also found this to sample tcp latency performance:
> https://code.google.com/p/paping/

Right; note that that measures time to establish a new connection, not
the delay of packets within an already established connection. My guess
would be that each established connection would have a new source port,
thus hashing into a new bin.

> Does fq_codel's flow classification supports external classifier
> filter? Say I only want to hash on dst port in my case.

I'm pretty sure it supports the normal classifier (tc filter). That
overrides the built-in hashing completely, but IIRC you can do your own
hashing in tc filter :)

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-12-05 23:25 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
2013-12-05 23:25                 ` Toke Høiland-Jørgensen [this message]
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=87fvq6c22z.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=codel@lists.bufferbloat.net \
    --cc=montedong@gmail.com \
    /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