From: Aaron Wood <woody77@gmail.com>
To: bloat <Bloat@lists.bufferbloat.net>
Subject: [Bloat] sch_fq pacing rate: Xbps, but at which layer in the network stack?
Date: Thu, 13 Apr 2017 20:12:05 -0700 [thread overview]
Message-ID: <CALQXh-MyNW-DnQZNVp9q-=5o1eye0u8T38vwEB-+3Q4jEEdvUQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
When I was testing with my iPerf changes, I realized that the sch_fq pacing
(which in iperf is set via setsockopt()), is pacing at a bandwidth that's
set at a pretty low level in the stack (which makes sense). This is
different from the application pacing that iperf does (which is pacing the
goodput).
But it's not clear to me where the X bps determination is being made. My
current guess is that it's at the interface level (since that's where
sch_fq is), and so it's approximately "bytes on the wire", minus preambles
and inter-packet spacing, and whatnot. And so it's including all the 802.x
headers involved (vlan tags, qos tags, source/dest macs, etc). Is this
correct?
-Aaron
[-- Attachment #2: Type: text/html, Size: 797 bytes --]
next reply other threads:[~2017-04-14 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 3:12 Aaron Wood [this message]
2017-04-14 18:00 ` Eric Dumazet
2017-04-14 23:38 ` Aaron Wood
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='CALQXh-MyNW-DnQZNVp9q-=5o1eye0u8T38vwEB-+3Q4jEEdvUQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=Bloat@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