From: Michal Soltys <nozo@ziu.info>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Question about HFSC atm+man patches
Date: Fri, 28 Nov 2008 00:17:47 +0100 [thread overview]
Message-ID: <492F2A9B.2050903@ziu.info> (raw)
In-Reply-To: <492E7B0B.8000601@trash.net>
Patrick McHardy wrote:
>
> Using different size tables for inner qdiscs is supposed to work.
> What is the "wrong size"? ->peek() should return a packet with the
> size the same as ->dequeue() would, which I think it does.
>
That's not what I meant.
((struct qdisc_skb_cb*)skb->cb)->pkt_len
This is the value returned by qdisc_pkt_len() (now used whenever length
is required, instead of skb->len), and it's recalculated during
qdisc_calculate_pkt_len() called from qdisc_enqueue() - if a qdisc has
stab. So the inner(most) qdisc with a size table, will be the last one
setting that field.
Now, if an outer qdisc, e.g. HFSC, does peek() or dequeue() later,
qdisc_pkt_len() will return overridden value.
If no qdiscs in "chain" have stab, then the field will be equal to
skb->len - which is set in qdisc_enqueue_root() (otherwise uninitialzed
value would be used later).
Am I seeing this right ?
next prev parent reply other threads:[~2008-11-27 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49292F54.4020803@ziu.info>
2008-11-23 14:05 ` Question about HFSC atm+man patches Patrick McHardy
2008-11-24 13:56 ` Michal Soltys
2008-11-24 14:11 ` Patrick McHardy
2008-11-24 23:21 ` Michal Soltys
2008-11-26 22:54 ` Michal Soltys
2008-11-27 10:48 ` Patrick McHardy
2008-11-27 23:17 ` Michal Soltys [this message]
2008-12-04 13:55 ` Question - size tables implementation Michal Soltys
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=492F2A9B.2050903@ziu.info \
--to=nozo@ziu.info \
--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).