From: Michal Soltys <soltys@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: Tue, 25 Nov 2008 00:21:01 +0100 [thread overview]
Message-ID: <492B36DD.8010701@ziu.info> (raw)
In-Reply-To: <492AB60A.9050606@trash.net>
Patrick McHardy wrote:
>
> qdisc_pkt_len already returns an adjusted length based on "size tables".
> Check out qdisc_enqueue()/qdisc_enqueue_root() for details.
>
> Is there something missing for overhead calculation?
Thanks for pointing that out. It will fit well.
I'll have to wrap my head around the sources first though (even if the
concept became even simpler now) - the patches for hfsc submitted in
July along the ones for size tables, were a bit more extensive compared
to what I've planned.
next prev parent reply other threads:[~2008-11-24 23:52 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 [this message]
2008-11-26 22:54 ` Michal Soltys
2008-11-27 10:48 ` Patrick McHardy
2008-11-27 23:17 ` Michal Soltys
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=492B36DD.8010701@ziu.info \
--to=soltys@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).