From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4A3843B2A4 for ; Wed, 27 Sep 2023 16:44:54 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1695847492; x=1696452292; i=moeller0@gmx.de; bh=+sJhRfSnpdLcOiroacxaf5+HQbrTp2SOaZTqbZPCO/k=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=MduJpQLCN8d0mz4niW7t0DcTMae7sIGxY+kJ9kMGjZrrFyvY31k4vANKaMHLlqYqBVWt2cCTfhj gIrF/LnvUtqcWsoc1kl/vlAouKhz/UXoIyrhy8KV70p7wE6Il4OBgchsvpW0LP1olXHIH/ew7rzMR nWtVo62rhvwNDiLx3q6Z1B8JxMKMvF7awE9edtdukzI0Gzmv80B+PaUXeWwKoqkEI8FsrMaKDZsUa gH/zDjV5H4/hYGWdj/u8lEpIvU+S/Pn0fbkPFZN0nSuLgQc5RWCqYNAffJg9tIp5svqlw2bPepMrv uN8wiZdmGyIYl+2KcV7jGycLp51WlvOHCxbQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from smtpclient.apple ([77.10.163.125]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M5fMY-1qjwiM0ixW-007D9E; Wed, 27 Sep 2023 22:44:52 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) From: Sebastian Moeller In-Reply-To: <20230927132732.6585172a@hermes.local> Date: Wed, 27 Sep 2023 22:44:51 +0200 Cc: Jan Rovner via Cake Content-Transfer-Encoding: quoted-printable Message-Id: <219B7A03-E587-43AF-8A98-B7872B3B525B@gmx.de> References: <20230927132732.6585172a@hermes.local> To: Stephen Hemminger X-Mailer: Apple Mail (2.3696.120.41.1.4) X-Provags-ID: V03:K1:p443yuyL6amFduXaXAxhKnMfvgZNf2YM+WeSGyj5ET+WdmHG7Ft 52kPYiQdBUQmODUc9B7F8KDkHhedXH2N4Xl0wHBUAxlOFt0zYxE8lJRPf5QDXADJBEkB6hK 4faUdrLDdeafcLqBSGrU24ja6LqOJHIrO62Y7Nv34OnWUb0VNAtjZ+i+cAqZ+y9Ecl0Kfh6 R3oIHqERCIVPhm5hNJzXA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:oWrP7i81gOw=;GOELJSpOmZVOWS1m4RdeTaU8YGQ 2jycYFYLwJs4L62kE1zWK9PjM1cRt0N6GfL1qIRIQn/F+rPFG0utSfGXgPJwxTJE5jdWQg+Kc gIixMZ9DLKtD/M6T82DP+Yy5NV34AdlVPXWZ5xpIb5Ly2rwOyT8KRbhfiNFylWQO1fVpMe3Pk s5i+awoldNldLIXVCmC/aiMnA+rCZbFSezQ4Px7sjJ0CuoJyO56aTiG4UpgMRER4YyFyXn2zW Tdyjh76VzMX63fWLIwj7cjKN9eeyB/bcucDIoTUEvZCvOQ+3XuX6I9Y1Y8GDrxFlp2jtozt7h KdRwOAYbuBi2jgL3zs1DESGx72Y6Rqz5y48pddVhTal6yEo2ri7kYdSwdmLGM1afYSZ5npYRD 54juN0WtoiV+SpXvpeGedmKsZR9HwVqqPSWp6cW6VOatsF+bJd8HlEbULjDuOsUZrjOyBg7Vp utiLmYKKZ1xVSpj54MhPZ0l0hUto2eTx8uZd3NDUQS221NdEIC27B8zJ5wBsn0JHrzQmksZs1 RdAfcQyuBXPUwbSjvESVaRnUvfrc3TqYa0LkPlawRatTb5/TuTZ6aQyAEWavkFt71kAIEiX// HmRw2tBFDgBtu9Oy+qWGf0bTOraXtUwC7YKgIjVao1mTVlgcLPGjX9EecYjvkMjuv6/IlD/Dq uMno/EY1lExScNRcQodswjTaQitqOLzyabrRpqbGMsaaL7JSuJRqPdTr2qZ/w5Ov1ZLtE6k3v /ntnae84d0VNqjSc8W69gG0F/qXE+joryK6uETdlUk6ubZlLdxSXVsI9Yu3cjFQ6TUAEBIRb3 lGbt25uMNL4Dx048LmE0wN1PfQldBuAeg7cr8etnwbp++3IBoYyQgXlKPWoKumzYqk22nRx6a iLO+nM4xVDE1D5949w6Nc/d4bt1uJhaDvwoL9RbILsOi1TUxNR2X0h2RKSboDH+6/GhCpHnDw 7xRM/BYugjC3Nx6sVBEEbkTE/7I= Subject: Re: [Cake] Cake - flow (or host) weight request - how to implement 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: Wed, 27 Sep 2023 20:44:54 -0000 Hi Stephen, > On Sep 27, 2023, at 22:27, Stephen Hemminger via Cake = wrote: >=20 > On Wed, 27 Sep 2023 17:48:06 +0000 > Jan Rovner via Cake wrote: >=20 >> Hello, >>=20 >> I am trying to experiment with sch_cake.c, my goal is to ad-hoc = prioritize / deprioritize traffic served to specified a host(s). The = prioritization would be controlled by an external system and it should = handle well the situation where a host has active flow(s). >=20 > Is it possible to use one or more existing BPF hooks to change DCSP = bits for that paths you wish to adjust. > The point is that changes to upstream base code are hard to maintain, = and that is what BPF initial hooks > were meant to provide. IIUC the OP wants not only to steer packets into a specific tier = but really wants to move a hash-bins complete state between tiers (he = talks about cobalt state). My (limited) understanding is that this would = need changes to cake's kernel code, either by always keeping shadow = cobalt state per hash-bin in all tiers or by implementing a state copy = procedure... Now, I am not sure how well moving flows around priority tiers = is going to work on a timescale that preserving the cobalt state seems = important and how to avoid re-ordering if a a flow is increased in = priority while it still has queued packets in the lower priority tier = (maybe the solution is moving both cobalt state and queued packets = between tiers). Regards Sebastian > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake