From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id EB8BE21F1BA for ; Sat, 28 Dec 2013 23:23:46 -0800 (PST) Received: from [192.168.2.41] ([79.202.2.233]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LqF9o-1VJSBT2AQi-00djZZ for ; Sun, 29 Dec 2013 08:23:44 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable From: Sebastian Moeller Date: Sun, 29 Dec 2013 08:23:32 +0100 To: Rich Brown , cerowrt-devel Message-ID: <2dda55ee-b40e-45c3-b973-2494f90ca182@email.android.com> X-Provags-ID: V03:K0:y7+UkfdhM5cMmgkWhvtLhTL44aG2KIL6XUD3vDL1mYxbQQ5s6IN lsh/L6ANBJMoMofrLGl9GVluiXXUJ9MmpYPgwfOwC7j4d1dWCUOJg5f4DkqcWW8IKf5jvTx o/kBpvIT0k4vKo54qSu7QVFAxR+YagzNCmeNoYvLKZgK3PtrbnRnELXhKIz14DPl7nTmX40 CNpfwESoqsIzcNJcnfVLw== Subject: Re: [Cerowrt-devel] SQM Question #1: How does SQM shape the ingress? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Dec 2013 07:23:47 -0000 Rich Brown wrote: >As I write the SQM page, I find I have questions that I can=E2=80=99t ans= wer >myself=2E I=E2=80=99m going to post these questions separately because th= ey=E2=80=99ll >each generate their own threads of conversation=2E > >QUESTION #1: How does SQM shape the ingress?=20 > >I know that fq_codel can shape the egress traffic by discarding traffic >for an individual flow that has dwelt in its queue for too long >(greater than the target)=2E Other queue disciplines use other metrics >for shaping the outbound traffic=2E=20 > >But how does CeroWrt shape the inbound traffic? (I have a sense that >the simple=2Eqos and simplest=2Eqos scripts are involved, but I=E2=80=99m= not sure >of anything beyond that=2E) So ingress shaping conceptually works just as egress shaping=2E Th= e shaper accepts packets at any speed from both directions but limits the s= peed used for transmitting them=2E So if your ingress natural bandwidth wou= ld be 100Mbit/s you would set the shaper to say 95Mbit/s, so the shaper wil= l create an internal artificial bottleneck just in front of its queue, so t= hat it can control the critical queue=2E Technically, this works by creating an artificial intermediate fun= ctional block device? (IFB), moving all ingress traffic to this device and = setting up classification and shaping on that device=2E I hope this helps=2E=2E=2E Sebastian > > >_______________________________________________ >Cerowrt-devel mailing list >Cerowrt-devel@lists=2Ebufferbloat=2Enet >https://lists=2Ebufferbloat=2Enet/listinfo/cerowrt-devel Hi Rich, --=20 Sent from my Android phone with K-9 Mail=2E Please excuse my brevity=2E