From: jamal <hadi@cyberus.ca>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
Robert Olsson <Robert.Olsson@data.slu.se>,
john.ronciak@intel.com, Ben Greear <greearb@candelatech.com>,
Auke Kok <auke-jan.h.kok@intel.com>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [e1000]: flow control on by default - good idea really?
Date: Tue, 04 Jul 2006 15:20:39 -0400 [thread overview]
Message-ID: <1152040839.5276.25.camel@jzny2> (raw)
In-Reply-To: <1152033116.5276.22.camel@jzny2>
On Tue, 2006-04-07 at 13:11 -0400, jamal wrote:
> CCing anybody who may have stakes on this. Ignore the email if this
> doesnt interest you.
> Ok, folks - i had deferred this discussion but it bit me in the ass.
> I just spend an hour debugging it (and in the process blew up a gbic i
> borrowed, so my day aint going well since i actually have to pay for
> this and cant really do the testing i was planning to;-<).
>
> I have a device connected to a e1000 that was erroneously advertising
> both tx/rx flow control but wasnt properly reacting to it.
> The default setup on the e1000 has rx flow control turned on.
> I was sending at wire rate gige from the device - which is about
> 1.48Mpps. The e1000 was in turn sending me flow control packets
> as per default/expected behavior. Unfortunately, it was sending
> a very large amount of packets. At one point i was seeing upto
> 1Mpps and on average, the flow control packets were consuming
> 60-70% of the bandwidth. Even when i fixed this behavior to act
> properly, allowing flow control on consumed up to 15% of the bandwidth.
> Clearly, this is a bad thing. Yes, the device in the first instance was
> at fault. But i have argued in the past that NAPI does just fine without
> flow control being turned on, so even chewing 5% of bandwidth on flow
> control is a bad thing..
>
> As a compromise, can we declare flow control as an advanced feature
> and turn it off by default? People who feel it is valuable and know
> what they are doing can turn it off.
I meant turn it on.
BTW, As an addendum this default behavior changed around 2.6.16 it
seems.
cheers,
jamal
next prev parent reply other threads:[~2006-07-04 19:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 17:11 [e1000]: flow control on by default - good idea really? jamal
2006-07-04 19:20 ` jamal [this message]
2006-07-05 16:23 ` Auke Kok
2006-07-05 20:37 ` Krzysztof Oledzki
2006-07-05 18:22 ` David Miller
2006-07-05 18:32 ` Auke Kok
2006-07-05 20:45 ` Krzysztof Oledzki
2006-07-05 21:13 ` Auke Kok
2006-07-06 13:03 ` jamal
2006-07-06 18:25 ` Auke Kok
2006-07-07 3:09 ` jamal
2006-07-07 6:59 ` David Miller
2006-07-07 12:28 ` jamal
2006-07-20 20:15 ` Bug in e1000 + semantics of flow control WAS(Re: " jamal
2006-08-03 12:29 ` jamal
2006-10-16 18:55 ` Auke Kok
2006-10-17 13:05 ` jamal
2006-10-17 17:18 ` Auke Kok
2006-10-17 18:25 ` Stephen Hemminger
2006-10-17 21:02 ` Auke Kok
2006-10-18 13:35 ` jamal
2006-10-18 14:57 ` Auke Kok
2006-10-17 21:46 ` David Miller
2006-07-05 16:57 ` Robert Olsson
2006-07-05 18:21 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 4:43 Michael Chan
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=1152040839.5276.25.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=Robert.Olsson@data.slu.se \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--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