From: Alessandro Bolletta <alessandro@mediaspot.net>
To: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: [Codel] Jumbo frames with fq_codel
Date: Mon, 25 Nov 2013 18:02:09 +0000 [thread overview]
Message-ID: <F52F175DFC537F48A43937B50B44BCA27A71EA14@EXCHANGE.mediaspot.local> (raw)
Hi guys,
I'm working on an environment which runs on jumbo ethernet frames (about 1550bytes) and I would ask you if do you think that it's needed a trick in order to correctly debloat interfaces as ath9k and ag71xx which carries such big frames.
Thanks
--
Alessandro Bolletta
Mediaspot S.r.l.
next reply other threads:[~2013-11-25 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 18:02 Alessandro Bolletta [this message]
2013-11-25 18:04 ` Jonathan Morton
2013-11-25 18:09 ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:08 ` [Codel] " Dave Taht
2013-11-25 18:17 ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:26 ` Dave Taht
2013-11-25 18:30 ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:32 ` [Codel] " Dave Taht
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=F52F175DFC537F48A43937B50B44BCA27A71EA14@EXCHANGE.mediaspot.local \
--to=alessandro@mediaspot.net \
--cc=codel@lists.bufferbloat.net \
/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