netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: "David S. Miller" <davem@davemloft.net>
Cc: Jamal Hadi Salim <hadi@cyberus.ca>, netdev@oss.sgi.com
Subject: [PATCH 0/5] PKT_SCHED: Convert Qdiscs to use generic network statistics/estimator
Date: Thu, 7 Oct 2004 03:01:46 +0200	[thread overview]
Message-ID: <20041007010146.GA18621@postel.suug.ch> (raw)

Dave,

This patchset converts Qdiscs to use the generic network
statistics/estimator. A new TLV type TCA_STATS2 is introduced
carrying the new statistics while the old TLV type TCA_STATS
is still provided for backward compatibility.

Patch 1: Replace tc_stats with new gnet_stats in struct Qdisc
Patch 2: Use gnet_stats API to copy statistics into netlink message
Patch 3: Introduce gen_replace_estimator
Patch 4: Use generic rate estimator
Patch 5: Qdisc are not supposed to dump TCA_STATS themselves

I tested these patches for a few days and didn't encounter
any problems. iproute2 is able to read out statistics via
backward compatibility. A slightly patched iproute2 can
read the new statistics.

             reply	other threads:[~2004-10-07  1:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07  1:01 Thomas Graf [this message]
2004-10-07  1:03 ` [PATCH 1/5] PKT_SCHED: Replace tc_stats with new gnet_stats in struct Qdisc Thomas Graf
2004-10-07  1:04 ` [PATCH 2/5] PKT_SCHED: Use gnet_stats API to copy statistics into netlink message Thomas Graf
2004-10-07  1:05 ` [PATCH 3/5] PKT_SCHED: Introduce gen_replace_estimator Thomas Graf
2004-10-07  1:07 ` [PATCH 4/5] PKT_SCHED: Use generic rate estimator Thomas Graf
2004-10-07  1:08 ` [PATCH 5/5] PKT_SCHED: Qdisc are not supposed to dump TCA_STATS themselves Thomas Graf
2004-10-09 15:48   ` jamal
2004-10-09 16:26     ` Thomas Graf
2004-10-09 16:41       ` jamal
2004-10-09 16:56         ` Thomas Graf
2004-10-20  1:19 ` [PATCH 0/5] PKT_SCHED: Convert Qdiscs to use generic network statistics/estimator David S. 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=20041007010146.GA18621@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).