From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Alpha Sparc <alphasparc@gmail.com>,
openwrt-devel <openwrt-devel@lists.openwrt.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] better ingress shaping somehow
Date: Fri, 3 Oct 2014 20:02:28 +0200 [thread overview]
Message-ID: <69F8425E-5376-43D1-9EDF-8142A863E1BF@gmx.de> (raw)
In-Reply-To: <CAA93jw5Sc0ujnwv-foPQ=iD5Jgfi08RTOR4OCd4t_qbuJ6i2mg@mail.gmail.com>
Hi Dave,
On Oct 3, 2014, at 01:07 , Dave Taht <dave.taht@gmail.com> wrote:
[cut a lot...]
> But: the real killer, on ingress shaping, is the call to skb_clone in
> sch_ingress->act_mirred path, I think.
So I thought that we basically have around 50Mbps “shaping-capability” on the wndrs which hew can distribute between egress and ingress, but if your analysis is correct wouldn’t that mean that shaping egress is cheaper? (Not that this has much relevance in the real world due uplink << downlink asymmetry the ISPs push onto us endusers)
>
> If it were possible to have sch_cake replace sch_ingress, that would
> be a huge win, but following the call path for why that must be cloned
> has thus far resisted my archeological expertise. An network ninja
> is needed here....
[…]
;)
Best Regards
Sebastian
next prev parent reply other threads:[~2014-10-03 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 23:07 Dave Taht
2014-10-03 0:57 ` William Katsak
2014-10-03 1:26 ` Dave Taht
2014-10-03 18:02 ` Sebastian Moeller [this message]
2014-10-05 16:26 ` Richard A. Smith
2014-10-05 17:57 ` Dave Taht
2014-10-06 2:16 ` Richard A. Smith
2014-10-06 2:37 ` Richard A. Smith
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69F8425E-5376-43D1-9EDF-8142A863E1BF@gmx.de \
--to=moeller0@gmx.de \
--cc=alphasparc@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=openwrt-devel@lists.openwrt.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