netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: torsten.schmidt@s2006.tu-chemnitz.de, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: add DiffServ priority based routing
Date: Thu, 14 Jan 2010 16:51:42 -0800 (PST)	[thread overview]
Message-ID: <20100114.165142.163322281.davem@davemloft.net> (raw)
In-Reply-To: <4B4F132B.7020001@gmail.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 14 Jan 2010 13:50:51 +0100

> Problem is, you might need many sets of counters...

Why nobody has suggested using existing kernel facilities for this is
beyond me.

We have a diffserv packet scheduler queueing discipline, so you can
classify traffic arbitrarily based upon the diffserv bits in the
packet and then shape them using that classification into different
packet scheduler queues.

Simply attach those child queues to that default pfifo qdisc, nothing
fancy.

Then you can dump the queue stats using 'tc'.

  reply	other threads:[~2010-01-15  0:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 13:32 [PATCH] ipv4: add DiffServ priority based routing Torsten Schmidt
2010-01-12 20:16 ` David Miller
2010-01-12 20:59   ` Philip A. Prindeville
2010-01-12 21:03     ` David Miller
2010-01-12 21:33       ` Philip A. Prindeville
2010-01-13  4:47         ` Steven Blake
2010-03-11 19:25       ` Philip A. Prindeville
2010-03-11 19:29         ` David Miller
2010-03-11 19:32           ` Philip A. Prindeville
2010-03-12 11:18           ` Benny Amorsen
2011-02-21  6:01             ` Philip Prindeville
2010-01-14 11:50   ` Torsten Schmidt
2010-01-14 12:50     ` Eric Dumazet
2010-01-15  0:51       ` David Miller [this message]
2010-01-15  8:24         ` Eric Dumazet
2010-01-15  8:26           ` David Miller

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=20100114.165142.163322281.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=torsten.schmidt@s2006.tu-chemnitz.de \
    /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).