From: Florian Westphal <fw@strlen.de>
To: Tom Herbert <therbert@google.com>
Cc: Florian Westphal <fw@strlen.de>,
Linux Netdev List <netdev@vger.kernel.org>,
Francois Romieu <romieu@fr.zoreil.com>,
Hayes Wang <hayeswang@realtek.com>
Subject: Re: [PATCH next] r8169: add support for Byte Queue Limits
Date: Tue, 30 Sep 2014 09:42:59 +0200 [thread overview]
Message-ID: <20140930074259.GC11709@breakpoint.cc> (raw)
In-Reply-To: <CA+mtBx8rpELodiiez8LkKupKBr9ynbQhrmAq8tcD4QKXHNjyaw@mail.gmail.com>
Tom Herbert <therbert@google.com> wrote:
> Watch inflight and limit in the byte_queue_limits for the queue.
> inflight must always go back to zero when link goes idle.
Yes, inflight goes to 0 when link is idle.
Output of
while true; do
for n in inflight limit; do
echo -n $n\ ; cat $n;
done; sleep 1;
done
during netperf run, 100mbit peer:
inflight 0
limit 3028
inflight 6056
limit 4542
[ no changes during test ]
limit 4542
inflight 3028
limit 6122
inflight 0
limit 6122
[ changed cable to 1gbit peer, restart netperf ]
inflight 37850
limit 36336
inflight 33308
limit 31794
inflight 33308
limit 31794
inflight 27252
limit 25738
[ no changes during test ]
inflight 27252
limit 25738
inflight 0
limit 28766
[ change cable to 100mbit peer, restart netperf ]
limit 28766
inflight 27370
limit 28766
inflight 4542
limit 5990
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 6056
limit 4542
inflight 0
[ end of test ]
I think thats what its supposed to look like :-)
next prev parent reply other threads:[~2014-09-30 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 20:56 [PATCH next] r8169: add support for Byte Queue Limits Florian Westphal
2014-09-29 21:00 ` Eric Dumazet
2014-09-29 21:03 ` Eric Dumazet
2014-09-29 21:05 ` Tom Herbert
2014-09-29 21:11 ` Florian Westphal
2014-09-29 21:49 ` Tom Herbert
2014-09-30 7:42 ` Florian Westphal [this message]
2014-10-01 4:57 ` Tom Herbert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140930074259.GC11709@breakpoint.cc \
--to=fw@strlen.de \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=therbert@google.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;
as well as URLs for NNTP newsgroup(s).