netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: netdev@vger.kernel.org
Cc: kernel-bugzilla@future.shiny.co.il,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 7278] New: forcedeth slowed down by traffic shaping
Date: Fri, 6 Oct 2006 17:22:17 -0700	[thread overview]
Message-ID: <20061006172217.af619871.akpm@osdl.org> (raw)
In-Reply-To: <200610070018.k970IDgF032404@fire-2.osdl.org>

On Fri, 6 Oct 2006 17:18:13 -0700
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=7278
> 
>            Summary: forcedeth slowed down by traffic shaping
>     Kernel Version: 2.6.16
>             Status: NEW
>           Severity: normal
>              Owner: jgarzik@pobox.com
>          Submitter: kernel-bugzilla@future.shiny.co.il
> 
> 
> When assigninig a simple Tocket Bucket Filter (TBF) classless trafic shaping
> policy to the eth0 device (provided by forcedeth), the device's upstream speed
> drops to ~12kbyte/s, regardless of the traffic limit I set in the shaping rule.
> In fact, the traffic limit values could be larger than the connection's
> throughput and it'll still limit to mere 12kbyte/s. Once I revert the rule to
> pfifo_fast, the rate resumes to the connection's real one (64kbyte/s).
> 
> If I set the TBF lower than 96kbit on eth0, it indeed applies; in other words, I
> can make the connection slower than 12kbyte/s but not faster.
> 
> If I assign the same rule to ppp0, it works just as intended, for rules higher
> than 12kbyte/s, leading me to believe forcedeth has something to do with it.
> 
> (Is there any module parameter I can try tweaking?)
> 

       reply	other threads:[~2006-10-07  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200610070018.k970IDgF032404@fire-2.osdl.org>
2006-10-07  0:22 ` Andrew Morton [this message]
2006-10-11 11:43   ` [Bugme-new] [Bug 7278] New: forcedeth slowed down by traffic shaping Jarek Poplawski
2006-10-11 11:51     ` Patrick McHardy

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=20061006172217.af619871.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=kernel-bugzilla@future.shiny.co.il \
    --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).