<br><br><div class="gmail_quote">On Mon, Mar 24, 2008 at 11:14 AM, Bruno Wolff III <<a href="mailto:bruno@wolff.to">bruno@wolff.to</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> ><br>
> > In case of dynamic throttling we won't be having any _fixed_ rate at which<br>
> > the connections assigned for updates will be able receive the packets. It<br>
> > means packets would be dropped frequently to implement policing. Isn't this<br>
> > waste of resources?<br>
<br>
</div>Yes and a protocol change was made to help. I believe this is the purpose of<br>
ECN (explicit congestion notification).<br>
<div class="Ih2E3d"><br>
> > Tools like tc and tcng implement queues to control outbound data. Is there<br>
> > any similar _kind of_ option available for inbound data?<br>
> > (Obviously we can't have queues because once the packet has been received<br>
> > must be processed)<br>
<br>
</div>Shaping on the wrong side of a link is problematic. You can implement queues<br>
on the receiving side which might allow you to better control which flows<br>
get slowed down using IFBs (which replace the older IMQs). While you can't<br>
absolutely prevent the other side from swamping the link with low priority<br>
packets, things should work reasonably with well behaved applications.<br>
<font color="#888888"><br></font></blockquote></div><br>Ingress shaping...sounds good! <br>Basically it is the way to implement policing efficiently?<br>-- <br>Regards,<br>Sunil Ghai