<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi All,</p>
<p>My brain woke up with this idea rattling around in it this
morning...obviously the subconscious has been busy. So here it
is:</p>
<p>Is there any way to use the egress drop signalling at ingress
time to drop stuff before it gets into the queue so then we don't
have to drop it at egress?</p>
<p>Something like: At enqueue if we've a matching flow check to see
if that flow had been in egress 'fast dropping' state *and* know
how much data in terms of time it had to fast drop to get the
queue back under the nominal time threshold. If say it had to
drop 10ms worth of packets to get back to the nominal 5ms
threshold then it dropped 67% of the packets/data. I'd like to
think of that as an 'unresponsive flow'...hence could it be
possible to use that information at ingress time and in essence
drop (some? 66%?) of them there, we can also signal congestion to
the stack at that point to (cake already does this signalling when
getting to its buffer size limit)</p>
<p><br>
</p>
<p>Probably a very silly idea.<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Thanks,
<a class="moz-txt-link-abbreviated" href="mailto:Kevin@Darbyshire-Bryant.me.uk">Kevin@Darbyshire-Bryant.me.uk</a>
M: +44 7947 355344 H: +44 1256 478597</pre>
</body>
</html>