CoDel AQM discussions
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Rick Jones <rick.jones2@hp.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] fq_codel : interval servo
Date: Fri, 31 Aug 2012 10:44:11 -0700	[thread overview]
Message-ID: <5040F7EB.5080909@freedesktop.org> (raw)
In-Reply-To: <5040F4E4.6000204@hp.com>

On 08/31/2012 10:31 AM, Rick Jones wrote:
> On 08/31/2012 10:15 AM, Jim Gettys wrote:
>> What is more, consumer ethernet switches do do flow control, whether you
>> want them to or not.
>
> My understanding is that Ethernet flow control (what ever its
> 802.1mumble might be?) is negotiated when the link is brought-up, and
> that both sides must agree before it will be active.  So, if you (the
> end station) do not want flow control, you can simply not accept it
> during link-up.
>
> Under Linux, the ethtool utility can be used to affect the
> configuration of "pause" (the name coming from the name of the frames
> used by flow control - "pause frames" if I recall correctly)

The cheap consumer switches typically have it on; and by default, most
ethernet drivers have it on by default.

That's how/why I found out about pause frames in the first place; I
wasn't looking for it, and the existence of these frames in wireshark
was a surprise to me.

This can cause "interesting" performance problems most consumers won't
understand when switches are layered.

Most enterprise switches will often have it off by default, or plain
never generate flow control frames at all.


                        - Jim



      reply	other threads:[~2012-08-31 17:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  6:55 Eric Dumazet
2012-08-31 13:41 ` Jim Gettys
2012-08-31 13:50 ` [Codel] [RFC] fq_codel : interval servo on hosts Eric Dumazet
2012-08-31 13:57   ` [Codel] [RFC v2] " Eric Dumazet
2012-09-01  1:37     ` Yuchung Cheng
2012-09-01 12:51       ` Eric Dumazet
2012-09-04 15:10         ` Nandita Dukkipati
2012-09-04 15:25           ` Jonathan Morton
2012-09-04 15:39             ` Eric Dumazet
2012-09-04 15:34           ` Eric Dumazet
2012-09-04 16:40             ` Dave Taht
2012-09-04 16:54               ` Eric Dumazet
2012-09-04 16:57               ` Eric Dumazet
2012-08-31 15:53 ` [Codel] fq_codel : interval servo Rick Jones
2012-08-31 16:23   ` Eric Dumazet
2012-08-31 16:59     ` Dave Taht
2012-09-01 12:53       ` Eric Dumazet
2012-09-02 18:08         ` Dave Taht
2012-09-02 18:17           ` Dave Taht
2012-09-02 23:28             ` Eric Dumazet
2012-09-02 23:23           ` Eric Dumazet
2012-09-03  0:18             ` Dave Taht
2012-08-31 16:40   ` Jim Gettys
2012-08-31 16:49     ` Jonathan Morton
2012-08-31 17:15       ` Jim Gettys
2012-08-31 17:31         ` Rick Jones
2012-08-31 17:44           ` Jim Gettys [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

  List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5040F7EB.5080909@freedesktop.org \
    --to=jg@freedesktop.org \
    --cc=codel@lists.bufferbloat.net \
    --cc=rick.jones2@hp.com \
    /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