From: Dave Taht <dave.taht@gmail.com>
To: netdev@vger.kernel.org
Cc: Dave Taht <dave.taht@gmail.com>
Subject: [PATCH net-next 0/2] Two small fq_codel optimizations
Date: Sat, 3 Aug 2019 16:37:27 -0700 [thread overview]
Message-ID: <1564875449-12122-1-git-send-email-dave.taht@gmail.com> (raw)
These two patches improve fq_codel performance
under extreme network loads. The first patch
more rapidly escalates the codel count under
overload, the second just kills a totally useless
statistic.
(sent together because they'd otherwise conflict)
Signed-off-by: Dave Taht <dave.taht@gmail.com>
Dave Taht (2):
Increase fq_codel count in the bulk dropper
fq_codel: Kill useless per-flow dropped statistic
net/sched/sch_fq_codel.c | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2019-08-03 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 23:37 Dave Taht [this message]
2019-08-03 23:37 ` [PATCH net-next 1/2] Increase fq_codel count in the bulk dropper Dave Taht
2019-08-03 23:37 ` [PATCH net-next 2/2] fq_codel: Kill useless per-flow dropped statistic Dave Taht
2019-08-06 21:18 ` [PATCH net-next 0/2] Two small fq_codel optimizations David Miller
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=1564875449-12122-1-git-send-email-dave.taht@gmail.com \
--to=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/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).