netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: David Miller <davem@davemloft.net>,
	kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH v2 2/3] net_sched: Add accessor function for packet length for qdiscs
Date: Fri, 25 Jul 2008 19:46:44 +0200	[thread overview]
Message-ID: <20080725174644.GA3005@ami.dom.local> (raw)
In-Reply-To: <20080725161503.67994cpfp4jouz7k@hayate.ip6>

On Fri, Jul 25, 2008 at 04:15:03PM +0300, Jussi Kivilinna wrote:
> Quoting "Jarek Poplawski" <jarkao2@gmail.com>:
...
>> Is it's really needed? Actually, if it's only for stats, I really
>> can't see the reason why not to get this info old way - before
>> enqueing? (And this could be not enough if we want packets count
>> like in htb.)
>>
>
> qdisc_enqueue recalculates packet size if inner qdisc has size table  
> set, so qdisc_pkt_len might return different length after qdisc_enqueue 
> than what it was before.

The question is how much does it matter for statistics. Packets' size
(and number) can change many times in many places. Does it mean all
these places should count the same or "real" size? But, if it's really
necessary here, IMHO, it should be done "clean" way, like additional
parameter(s) to qdisc_enqueue(), because in cases like NET_XMIT_CN we
don't even know what happened with an skb.

Jarek P.

  reply	other threads:[~2008-07-25 17:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 23:34 [PATCH v2 0/3] Add size table feature for qdiscs Jussi Kivilinna
2008-07-19 23:35 ` [PATCH v2 1/3] net_sched: Add qdisc_enqueue wrapper Jussi Kivilinna
2008-07-19 23:35 ` [PATCH v2 2/3] net_sched: Add accessor function for packet length for qdiscs Jussi Kivilinna
2008-07-25 10:57   ` Jarek Poplawski
2008-07-25 10:57     ` David Miller
2008-07-25 11:37       ` Jarek Poplawski
2008-07-25 11:49         ` David Miller
2008-07-26 13:21           ` Patrick McHardy
2008-07-26 14:18             ` Jarek Poplawski
2008-07-30 10:47               ` Patrick McHardy
2008-07-30 11:19                 ` Jarek Poplawski
2008-07-30 11:21                   ` Patrick McHardy
2008-07-30 11:37                     ` Jarek Poplawski
2008-07-30 11:40                       ` Patrick McHardy
2008-07-30 11:48                         ` David Miller
2008-07-30 11:52                           ` Patrick McHardy
2008-07-30 12:19                             ` Jarek Poplawski
2008-07-30 20:50                             ` Jarek Poplawski
2008-07-25 11:53         ` Jarek Poplawski
2008-07-25 11:52           ` David Miller
2008-07-25 12:08             ` Jarek Poplawski
2008-07-25 12:16               ` David Miller
2008-07-25 12:29         ` Jussi Kivilinna
2008-07-25 12:54           ` Jarek Poplawski
2008-07-25 13:15             ` Jussi Kivilinna
2008-07-25 17:46               ` Jarek Poplawski [this message]
2008-07-25 18:02                 ` Jarek Poplawski
2008-07-19 23:35 ` [PATCH v2 3/3] net_sched: Add size table " Jussi Kivilinna
2008-07-20  7:09 ` [PATCH v2 0/3] Add size table feature " 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=20080725174644.GA3005@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.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).