General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] RPM for sqm-scripts
Date: Wed, 31 Jul 2019 21:37:23 +0200	[thread overview]
Message-ID: <B7537C85-D0FE-4F95-A039-82D9B25DEB03@gmx.de> (raw)
In-Reply-To: <92FC145B7421C60FA15458F4@[192.168.1.16]>



> On Jul 31, 2019, at 21:32, Kenneth Porter <shiva@sewingwitch.com> wrote:
> 
> I decided to try the sqm-scripts and created an RPM to make it easy to install/upgrade/uninstall on my CentOS 7 system. Here's the result:
> 
> <https://sewingwitch.com/ken/Stuff/sqm-scripts/>

	Pretty cool! (Caveat: due to lack of a centos system I will not be able to actually test it)


> 
> An initial attempt at using simple.qos on my system killed performance and the interface became unusuable, but I was probably too optimistic in setting the bandwidth numbers based on best response from speedtest-cli. I temporarily disabled it until I can test during off-hours.

	So maybe run the following to get some debug output:

SQM_DEBUG=1 SQM_VERBOSITY_MAX=10 /etc/init.d/sqm start ; tc -s qdisc ; tc -d qdisc ; SQM_DEBUG=1 SQM_VERBOSITY_MAX=10 /etc/init.d/sqm stop

I would hope that this should undo its damage at the end but will also capture the wedged state in between. Then again this still might lead to an unusable interface....


Best Regards
	Sebastian

> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2019-07-31 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 19:32 Kenneth Porter
2019-07-31 19:37 ` Sebastian Moeller [this message]
2019-07-31 20:01   ` Kenneth Porter
2019-08-08 14:07 ` Toke Høiland-Jørgensen

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=B7537C85-D0FE-4F95-A039-82D9B25DEB03@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=shiva@sewingwitch.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