netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@oss.sgi.com, shemminger@osdl.org
Subject: Re: RFC/PATCH capture qdisc requeue event in stats
Date: Wed, 29 Sep 2004 14:48:32 +0200	[thread overview]
Message-ID: <20040929124832.GA9634@postel.suug.ch> (raw)
In-Reply-To: <1096426464.1045.133.camel@jzny.localdomain>

* jamal <1096426464.1045.133.camel@jzny.localdomain> 2004-09-28 22:54
> Lets do it on gnet stats though so we can make it more accessible.
> I think your granularity maybe too thin: bytes,packets, drops
> may need to be in the same TLV.

I partially agree as long as no structs visible to userspace will
ever change after introduction.

I'd really like to avoid maintaining different structs for collection
and transfer which must be kept in sync.

Having the application do its own struct and fill it based on
if (tb[TCA_STATS_*]) conditions avoids all possible compatibility 
issues. It would be possible for the application to choose between
the original and a _64 variant if we ever introduce them.

So this would be my approach:

Leave gnet_stats as-is and extend it as needed but hide it from
userspace.

Extend gen_copy_stats to add a nested TLV for every stat in
the structure. We could even introduce a bitmap to allow the
struct gnet_stats user to define which statistics are defined
and which aren't. This way we could avoid the mess with pfifo
and bfifo both using backlog but with a different unit in mind
(packets/bytes).

> do you have cycles to run with that patch?

Yes, it is related to my work so it's not a problem.

  reply	other threads:[~2004-09-29 12:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 17:13 RFC/PATCH capture qdisc requeue event in stats jamal
2004-08-30 21:40 ` David S. Miller
2004-08-30 22:14   ` jamal
2004-08-30 22:44     ` David S. Miller
2004-08-30 22:56       ` jamal
2004-08-30 23:00         ` David S. Miller
2004-08-31  1:43           ` jamal
2004-08-31  2:17             ` David S. Miller
2004-08-31  2:37               ` jamal
2004-08-31  4:29                 ` David S. Miller
2004-08-31 18:09                   ` jamal
2004-09-29  0:36                   ` Thomas Graf
2004-09-29  2:54                     ` jamal
2004-09-29 12:48                       ` Thomas Graf [this message]
2004-09-29 14:08                         ` jamal
2004-08-30 23:05         ` Stephen Hemminger
2004-09-28 23:10 ` Stephen Hemminger
2004-09-28 23:18   ` David S. Miller
2004-09-29  0:01     ` Stephen Hemminger
2004-09-29  0:03       ` David S. Miller
2004-09-29  2:31         ` jamal

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=20040929124832.GA9634@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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).