All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB, MPU, and suitable values
Date: Tue, 25 May 2004 21:35:33 +0000	[thread overview]
Message-ID: <40B3BC25.60604@wildgooses.com> (raw)
In-Reply-To: <200405171634.02092.jasonb@edseek.com>

Andreas Klauer wrote:

>Am Tuesday 18 May 2004 08:38 schrieb Ed Wildgoose:
>  
>
>>I would code this as:
>>
>>size = (  (int)((datasize-1)/48) + 1) * 53
>>
>>You could hardcode something similar into your tc and see if it helps
>>(just remove PMU and overhead code added by the existing patch).
>>    
>>
>
>How does modifying the tc code affect the way rates are calculated and 
>limited in the kernel? Isn't it just a userspace tool to create qdisc / 
>class structures and read statistics?
>  
>

Dunno, haven't had time to read through the code much.  It started 
because someone earlier in this thread pointed out that there was a 
patch available on the tc website to better handle overhead and MPU.  I 
just altered the patch in a different way based on what looked fairly 
obvious.

However, I notice that tc is noted to "have a full implementation of HTB 
inside it".  Perhaps there are two HTB implementations kicking around?

If I get a chance I will have a poke around in the code.  If the flow is 
this straightforward in most of the kernel modules then it looks pretty 
straightforward to implement some options to control padding packets to 
simulate the underlying protocol.  However, since no one else has done 
it, I doubt it is so...

Ed W

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-05-25 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 20:34 [LARTC] HTB, MPU, and suitable values Jason Boxman
2004-05-17 21:23 ` Ed Wildgoose
2004-05-17 22:04 ` Jason Boxman
2004-05-18  6:38 ` Ed Wildgoose
2004-05-25 19:48 ` Andreas Klauer
2004-05-25 21:35 ` Ed Wildgoose [this message]

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=40B3BC25.60604@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.