From: "Richard Scheffenegger" <rscheff@gmx.at>
To: "Kevin Gross" <kevin.gross@avanw.com>, <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Jumbo frames and LAN buffers
Date: Mon, 16 May 2011 20:36:57 +0200 [thread overview]
Message-ID: <60A7498C842645FBB11A58BAA9467ACD@srichardlxp2> (raw)
In-Reply-To: <012d01cc13cb$61617ed0$24247c70$@gross@avanw.com>
Kevin,
> My understanding is that 802.1au, "lossless Ethernet", was designed
> primarily to allow Fibre Channel to be carried over 10 GbE so that SAN and
> LAN can share a common infrastructure in datacenters. I don't believe
> anyone
> intends for it to be enabled for traffic classes carrying TCP.
Well, QCN requires a L2 MAC sender, network and receiver cooperation (thus
you need fancy "CNA" converged network adapters, to start using it - these
would be reaction/reflection points; plus the congestion points - switches -
would need HW support too; nothing one can buy today; higher-grade
(carrier?) switches may have the reaction/reflection points built into them,
and could use legacy 802.3x signalling outside the 802.1Qau cloud).
The following may be too simplistic
Once the hardware has a reaction point support, it classifies traffic, and
calculates the per flow congestion of the path (with flow really being the
classification rules by the sender), the intermediates / receiver sample the
flow and return the congestion back to the sender - and within the sender, a
token bucket-like rate limiter will adjust the sending rate of the
appropriate flow(s) to adjust to the observed network conditions.
http://www.stanford.edu/~balaji/presentations/au-prabhakar-qcn-description.pdf
http://www.ieee802.org/1/files/public/docs2007/au-pan-qcn-details-053007.pdf
The congestion control loop has a lot of similarities to TCP CC as you will
note...
Also, I haven't found out how fine-grained the classification is supposed to
be (per L2 address pair? Group of flows? Which hashing then to use for
mapping L2 flows into those groups between reaction/congestion/reflection
points...).
Anyway, for the here and now, this is pretty much esoteric stuff not
relevant in this context :)
Best regards,
Richard
----- Original Message -----
From: "Kevin Gross" <kevin.gross@avanw.com>
To: <bloat@lists.bufferbloat.net>
Sent: Monday, May 16, 2011 3:15 PM
Subject: Re: [Bloat] Jumbo frames and LAN buffers
> All the stand-alone switches I've looked at recently either do not support
> 802.3x or support it in the (desireable) manner described in the last
> paragraph of the linked blog post. I don't believe Ethernet flow control
> is
> a factor in current LANs. I'd be interested to know the specifics if
> anyone
> sees it differently.
>
> My understanding is that 802.1au, "lossless Ethernet", was designed
> primarily to allow Fibre Channel to be carried over 10 GbE so that SAN and
> LAN can share a common infrastructure in datacenters. I don't believe
> anyone
> intends for it to be enabled for traffic classes carrying TCP.
>
> Kevin Gross
>
> -----Original Message-----
> From: bloat-bounces@lists.bufferbloat.net
> [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Jim Gettys
> Sent: Monday, May 16, 2011 5:24 AM
> To: bloat@lists.bufferbloat.net
> Subject: Re: [Bloat] Jumbo frames and LAN buffers
>
> Not necessarily out of knowledge or desire (since it isn't usually
> controllable in the small switches you buy for home). It can cause
> trouble even in small environments as your house.
>
> http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html
>
> I know I'm at least three consumer switches deep, and it's not by choice.
> - Jim
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
next prev parent reply other threads:[~2011-05-16 18:27 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:05 [Bloat] Network computing article on bloat Dave Taht
2011-04-26 18:13 ` Dave Hart
2011-04-26 18:17 ` Dave Taht
2011-04-26 18:28 ` dave greenfield
2011-04-26 18:32 ` Wesley Eddy
2011-04-26 19:37 ` Dave Taht
2011-04-26 20:21 ` Wesley Eddy
2011-04-26 20:30 ` Constantine Dovrolis
2011-04-26 21:16 ` Dave Taht
2011-04-27 17:10 ` Bill Sommerfeld
2011-04-27 17:40 ` Wesley Eddy
2011-04-27 7:43 ` Jonathan Morton
2011-04-30 15:56 ` Henrique de Moraes Holschuh
2011-04-30 19:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Richard Scheffenegger
2011-05-05 16:01 ` Jim Gettys
2011-05-05 16:10 ` Stephen Hemminger
2011-05-05 16:30 ` Jim Gettys
2011-05-05 16:49 ` [Bloat] Burst Loss Neil Davies
2011-05-05 18:34 ` Jim Gettys
2011-05-06 11:40 ` Sam Stickland
2011-05-06 11:53 ` Neil Davies
2011-05-08 12:42 ` Richard Scheffenegger
2011-05-09 18:06 ` Rick Jones
2011-05-11 8:53 ` Richard Scheffenegger
2011-05-11 9:53 ` Eric Dumazet
2011-05-12 14:16 ` [Bloat] Publications Richard Scheffenegger
2011-05-12 16:31 ` [Bloat] Burst Loss Fred Baker
2011-05-12 16:41 ` Rick Jones
2011-05-12 17:11 ` Fred Baker
2011-05-13 5:00 ` Kevin Gross
2011-05-13 14:35 ` Rick Jones
2011-05-13 14:54 ` Dave Taht
2011-05-13 20:03 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Kevin Gross
2011-05-14 20:48 ` Fred Baker
2011-05-15 18:28 ` Jonathan Morton
2011-05-15 20:49 ` Fred Baker
2011-05-16 0:31 ` Jonathan Morton
2011-05-16 7:51 ` Richard Scheffenegger
2011-05-16 9:49 ` Fred Baker
2011-05-16 11:23 ` [Bloat] Jumbo frames and LAN buffers Jim Gettys
2011-05-16 13:15 ` Kevin Gross
2011-05-16 13:22 ` Jim Gettys
2011-05-16 13:42 ` Kevin Gross
2011-05-16 15:23 ` Jim Gettys
[not found] ` <-854731558634984958@unknownmsgid>
2011-05-16 13:45 ` Dave Taht
2011-05-16 18:36 ` Richard Scheffenegger [this message]
2011-05-16 18:11 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Richard Scheffenegger
2011-05-17 7:49 ` BeckW
2011-05-17 14:16 ` Dave Taht
[not found] ` <-4629065256951087821@unknownmsgid>
2011-05-13 20:21 ` Dave Taht
2011-05-13 22:36 ` Kevin Gross
2011-05-13 22:08 ` [Bloat] Burst Loss david
2011-05-13 19:32 ` Denton Gentry
2011-05-13 20:47 ` Rick Jones
2011-05-06 4:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Fred Baker
2011-05-06 15:14 ` richard
2011-05-06 21:56 ` Fred Baker
2011-05-06 22:10 ` Stephen Hemminger
2011-05-07 16:39 ` Jonathan Morton
2011-05-08 0:15 ` Stephen Hemminger
2011-05-08 3:04 ` Constantine Dovrolis
2011-05-08 13:00 ` Richard Scheffenegger
2011-05-08 12:53 ` Richard Scheffenegger
2011-05-08 12:34 ` Richard Scheffenegger
2011-05-09 3:07 ` Fred Baker
2011-05-16 18:40 [Bloat] Jumbo frames and LAN buffers Richard Scheffenegger
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60A7498C842645FBB11A58BAA9467ACD@srichardlxp2 \
--to=rscheff@gmx.at \
--cc=bloat@lists.bufferbloat.net \
--cc=kevin.gross@avanw.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