From: Dave Taht <dave.taht@gmail.com>
To: Kevin Gross <kevin.gross@avanw.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Jumbo frames and LAN buffers
Date: Mon, 16 May 2011 07:45:03 -0600 [thread overview]
Message-ID: <BANLkTi=sYohPozpa1s+rnOpzWjS8P5mt0Q@mail.gmail.com> (raw)
In-Reply-To: <-854731558634984958@unknownmsgid>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
On Mon, May 16, 2011 at 7:42 AM, Kevin Gross <kevin.gross@avanw.com> wrote:
> I would like to try this. Can you suggest specific equipment to look at.
> Due
> to integration and low port count, most of the cheap consumer stuff has
> surprisingly good layer-2 performance. I've tested a bunch of Linksys and
> other small/medium business 5 to 24 port gigabit switches. Since I measure
> latency, I expect I would have noticed if flow control were kicking in.
>
I would certainly appreciate more people looking at the switch in the
wndr3700v2 we're using on the bismark project.
I'm seeing some pretty deep buffering on it
>
> 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 7:23 AM
> To: bloat@lists.bufferbloat.net
> Subject: Re: [Bloat] Jumbo frames and LAN buffers
>
> On 05/16/2011 09:15 AM, Kevin Gross wrote:
> > 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.
>
> Heh. Plug wireshark into current off the shelf cheap consumer switches
> intended for the home. You won't like what you see. And you have no
> way to manage them. I was quite surprised last fall when doing my home
> experiments to see 802.3 frames; I had been blissfully unaware of its
> existence, and had to go read up on it as a result.
>
> I don't think any of the enterprise switches are so brain damaged. So i
> suspect it's mostly lurking to cause trouble in home and small office
> environments, exactly where no-one will know what's going on.
> - Jim
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 3233 bytes --]
next prev parent reply other threads:[~2011-05-16 13:35 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 [this message]
2011-05-16 18:36 ` Richard Scheffenegger
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='BANLkTi=sYohPozpa1s+rnOpzWjS8P5mt0Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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