From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: dag dg <dagofthedofg@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Need Guidance on reducing bufferbloat on a Fedora-based router
Date: Sat, 20 Jan 2018 18:55:26 +0100 [thread overview]
Message-ID: <877esc2z5d.fsf@toke.dk> (raw)
In-Reply-To: <CAO2Qn5nxMRC_MkO6SY+NwhX2Wq_P8S=Zr_ay+-HLZdn91a8JBw@mail.gmail.com>
dag dg <dagofthedofg@gmail.com> writes:
> At this point I'm just looking for some guidance on steps to move
> forward, any suggestions would be appreciated.
From your email I'm not quite sure what problem it is you are trying to
solve? You say that sqm-scripts with fq_codel has gotten your
bufferbloat under control, so what is the problem, exactly? :)
-Toke
next prev parent reply other threads:[~2018-01-20 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 17:51 dag dg
2018-01-20 17:55 ` Toke Høiland-Jørgensen [this message]
[not found] ` <CAO2Qn5moEDwf1tuadG5vtE04LCvGms3UgmNLHSkQ+2Au5fXFiQ@mail.gmail.com>
2018-01-20 19:22 ` 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=877esc2z5d.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dagofthedofg@gmail.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