netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] hfsc: add link layer overhead adaption
Date: Mon, 23 Jun 2008 13:27:26 +0200	[thread overview]
Message-ID: <485F889E.1050901@trash.net> (raw)
In-Reply-To: <20080623142417.9gxuu3y9r4084s4c@hayate.ip6>

Jussi Kivilinna wrote:
> Quoting Patrick McHardy <kaber@trash.net>:
>>
>> This looks like an abuse of rate tables, which usually convert
>> packet sizes to transmission times. You undo that above using
>> expensive calculations.
>>
>> I think this should be done by performing the length calculation
>> in the kernel directly.
> 
> Yes, it's abuse, and actually table is created using false rate (rate = 
> PSCHED_TICKS_PER_SEC) so div_u64 is avoided. Div_u64 is there just in 
> case something goes wrong in userspace. Using rate table allows 
> changes/updates to link layer emulation with only userspace updates 
> avoiding, but maybe abuse of rate table isn't right way to do this after 
> all.
> 
> So would it be better if I add 'length table' to kernel&userspace and 
> use it instead?

Yes, I even posted an unfinished patch for this one or two years
ago, in response to the overhead calculation patches for HTB etc.

I can't find it right now, but haven't tried too hard. It was
called qdisc STABs (for size tables), you should be able to find
it in the archives.

  reply	other threads:[~2008-06-23 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 10:25 [PATCH] hfsc: add link layer overhead adaption Jussi Kivilinna
2008-06-23 10:57 ` Patrick McHardy
2008-06-23 11:24   ` Jussi Kivilinna
2008-06-23 11:27     ` Patrick McHardy [this message]
2008-06-23 19:15       ` Jussi Kivilinna
2008-06-23 19:37         ` Patrick McHardy
2008-06-23 22:29           ` Jussi Kivilinna

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=485F889E.1050901@trash.net \
    --to=kaber@trash.net \
    --cc=jussi.kivilinna@mbnet.fi \
    --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).