From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] the de-evolution of rpm
Date: Thu, 13 Apr 2023 15:13:23 -0700 [thread overview]
Message-ID: <CAA93jw7ohF3ep4XfgRJecCqD-hT0H58em=76+ho_=p8ayhHY3A@mail.gmail.com> (raw)
I have not been paying a lot of attention here of late. I objected to
the enormous number of flows goresponsiveness was doing, and strongly
suggested it run to time of first loss or mark. I find 4 flows enough
to stress out a network. Anyway, is the structure of networkQuality
changing any in ippm? Some context here:
https://www.reddit.com/r/amazoneero/comments/12ksu9d/sqm_optimizing_for_videoconferencing_and_gaming/jg4zsq2/?context=8&depth=9
--
AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2023-04-13 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 22:13 Dave Taht [this message]
2023-04-14 20:15 ` Christoph Paasch
2023-04-14 21:02 ` Dave Taht
2023-04-14 21:17 ` Christoph Paasch
2023-04-14 21:26 ` [Rpm] Vote: Closing the rpm list? Dave Taht
2023-04-15 0:03 ` Frantisek Borsik
2023-04-15 0:18 ` Dave Taht
2023-04-15 0:29 ` JAMES R CUTLER
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7ohF3ep4XfgRJecCqD-hT0H58em=76+ho_=p8ayhHY3A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=rpm@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