From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 933873B29E for ; Thu, 7 Mar 2019 13:31:30 -0500 (EST) Received: by mail-vk1-xa29.google.com with SMTP id l62so3955531vkh.0 for ; Thu, 07 Mar 2019 10:31:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZcRFBQWyvxSkQygO+rMjf7jkOuodAEq/g0jNw50nWD4=; b=aknENhfij9bNIWM9lkvhblOJtdoBHjUz6X1LtCYMucSAa2GqME82pFpucmH4Awqjp9 zBBvqyhaHl4i1zurRAPmxyeiU35qPysoM7xOGT22x/1bZ7u1NBXO0HaCnsF2oz2JxxX5 vLNnh/1ntvjH3tzJKTMCy0GsyXwj4IZYYwOCCUfUtr9WGAdzVPRQfks2f87JXqdtwadV 8sIV6Q06hAmQ5+lfvkfYFKfZu7olb4oQm57RsDGlki3Bqhh07UYzBPHjtHK28TTh/R7b 9yrfVmu81FHBPZN6liteR7JkXohoSiP3vanbAtcB5gkL2d5xQS9RRYFGkJBkh3VOjf5h 2FgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZcRFBQWyvxSkQygO+rMjf7jkOuodAEq/g0jNw50nWD4=; b=EHtG6RiDANv39TjuTOGC3QBogJ0mWff32aMDM7YaMePLrSFgk8UJ9EsqQ0v6tYS/dx I36zyfEPlyPhZgNpUCpaTF5VinWSbnF7Q1a6d4tHX1I5usjwlitsBrQ3O+wWk3B+oi4F hWh0oBljxBu6zuLGzkmlKvRfuFHec7vE5nWEFiOwtm7J2SI5xFxTnUdj3aKRNniymjQP 1gdfDBB768WecS76zsR6hfe7YlXGwb7SNsHUTXKL1ygHX9j2UIO5kKmbYhxYHW2M9pz+ Vz+ErdDMsWMl/t+exGsAoDiLTPxmBcWeBcwQF4hT6IvziI6GQyrWUrtNneGHuys66Lnp /Pug== X-Gm-Message-State: APjAAAUtTbt7m9m42BAdoUZ7WURIjqKcFcaHCDkYfEUCKQ8b1y4P0uEN 4W+EqHR3gX/LXHnSLw8ZM0ix+2klIRgieueEnEmJqQ== X-Google-Smtp-Source: APXvYqyn73PRp5/aRgSPTSE1xE2TwB4R+Shcd0AUc4sqT9QHR5OC4Fr1P/y7tHAzFIkQdHUC7thsTC/A45H2WEyL798= X-Received: by 2002:a1f:82ce:: with SMTP id e197mr7109515vkd.89.1551983490058; Thu, 07 Mar 2019 10:31:30 -0800 (PST) MIME-Version: 1.0 References: <8736nz11mt.fsf@toke.dk> <87o96nyo1n.fsf@toke.dk> <87lg1r0xp0.fsf@toke.dk> <87h8cf0wt7.fsf@toke.dk> <87ef7j0vui.fsf@toke.dk> <875zsu1quw.fsf@toke.dk> In-Reply-To: <875zsu1quw.fsf@toke.dk> From: Martin Zaharinov Date: Thu, 7 Mar 2019 20:31:19 +0200 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Pete Heist , =?UTF-8?Q?Toke_H=C3=B8iland=2DJ=C3=B8rgensen_via_Cake?= Content-Type: multipart/alternative; boundary="0000000000009f524b058385501a" Subject: Re: [Cake] Bug or not Cake + hfsc or Cake + Drr X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2019 18:31:30 -0000 --0000000000009f524b058385501a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes Toke i know i will make more test and will write Best regards, m. On Thu, Mar 7, 2019 at 8:28 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Martin Zaharinov writes: > > > Hi Pete > > yes i find this patch and add to cake source > > and in my test with hfsc and cake > > i use > > > > tc qdisc add dev eth1 root handle 1: hfsc default 1 > > tc class add dev eth1 parent 1: classid 1:1 hfsc ls rate 7mbit ul rate > 7mbit > > tc qdisc add dev eth1 parent 1:1 cake besteffort bandwidth 5mbit > datacentre > > nat memlimit 32m > > > > user speed is 5mbit and on hfsc i add extra 2 mbit to give free limit f= or > > cake. > > and work fine but in dmesg get : > > > > [44835.530255] qdisc_peek_len: cake qdisc 8017: is non-work-conserving? > > [44840.689403] HFSC: cake qdisc 8012: is non-work-conserving? > > Yes. As I said, you *cannot use the cake shaper* when running in under > HFSC. > > > user receive 5mbit for upload and download and fine work. > > mai be need to add no-split-gso to config > > > > but after add have same error on dmesg : > > > > [44955.641391] HFSC: cake qdisc 8021: is non-work-conserving? > > [44955.958904] HFSC: cake qdisc 801C: is non-work-conserving? > > > > but work fine and will remove warrning from kernel source to not list i= n > > dmesg :) > > I very much doubt that things will just continue to "work fine" if you > just remove the warning... > > -Toke > --0000000000009f524b058385501a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes Toke i know=C2=A0
i will make mor= e test and will write=C2=A0

Best regards,
m.


On Thu, Mar 7, 2019 at 8:28 PM Toke H= =C3=B8iland-J=C3=B8rgensen <toke@redh= at.com> wrote:
Martin Zaharinov <micron10@gmail.com> writes:

> Hi Pete
> yes i find this patch and add to cake source
> and in my test with hfsc and cake
> i use
>
> tc qdisc add dev eth1 root handle 1: hfsc default 1
> tc class add dev eth1 parent 1: classid 1:1 hfsc ls rate 7mbit ul rate= 7mbit
> tc qdisc add dev eth1 parent 1:1 cake besteffort bandwidth 5mbit datac= entre
> nat memlimit 32m
>
> user speed is 5mbit and on hfsc i add extra 2 mbit to give free limit = for
> cake.
> and work fine but in dmesg get :
>
> [44835.530255] qdisc_peek_len: cake qdisc 8017: is non-work-conserving= ?
> [44840.689403] HFSC: cake qdisc 8012: is non-work-conserving?

Yes. As I said, you *cannot use the cake shaper* when running in under
HFSC.

> user receive 5mbit for upload and download and fine work.
> mai be need to add no-split-gso to config
>
> but after add have same error on dmesg :
>
> [44955.641391] HFSC: cake qdisc 8021: is non-work-conserving?
> [44955.958904] HFSC: cake qdisc 801C: is non-work-conserving?
>
> but work fine and will remove warrning from kernel source to not list = in
> dmesg :)

I very much doubt that things will just continue to "work fine" i= f you
just remove the warning...

-Toke
--0000000000009f524b058385501a--