<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 28, 2018, at 10:56 AM, Toke Høiland-Jørgensen <<a href="mailto:toke@toke.dk" class="">toke@toke.dk</a>> wrote:</div><div class=""><div class=""><br class="">Note that with the existing tc classifier stuff we already added to<br class="">Cake, we basically have this already (eBPF can map traffic to tin and<br class="">flow however it pleases).<br class=""></div></div></blockquote><div><br class=""></div><div>Sorry, this just jostled in my brain now that I may be able to implement member fairness today, based on what you wrote earlier in a thread that I entirely missed: <a href="https://lists.bufferbloat.net/pipermail/cake/2018-May/003811.html" class="">https://lists.bufferbloat.net/pipermail/cake/2018-May/003811.html</a></div><div><br class=""></div><div>George posted an example of assigning packets to a tin: <a href="https://lists.bufferbloat.net/pipermail/cake/2018-May/003809.html" class="">https://lists.bufferbloat.net/pipermail/cake/2018-May/003809.html</a></div><div><br class=""></div><div>How does one send packets to a specific flow / queue?</div><div><br class=""></div><div>This wouldn’t give both per-member and per-flow fairness, but at least per-member fairness might be possible. There are 1024(?) queues available and 800 members, so I’m just speculating that I could map members to a number from 0 to 800 (active member IDs packed and zero-based would work) and assign each member to their own flow. Thanks... :)</div></div><br class=""></body></html>