<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="">Adam,<br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div><div><blockquote type="cite" class=""><div class="">On 2 Sep 2019, at 19:42, <a href="mailto:adamv0025@netconsultings.com" class="">adamv0025@netconsultings.com</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">You nailed it, <br class="">Actually very few line-cards or fabric-less boxes with (run to completion<br class="">vendor chips) out there do line-rate at 64B packets nowadays.<br class="">-with the advent of 100G the "line-rate at 64B" is pretty much not a thing<br class="">anymore...<br class="">Something to consider, not because one wants to push 64B packets at<br class="">line-rate on all ports but because one needs to push IMIX through QOS or<br class="">filters... and the card/box might simply not deliver.<br class=""></div></div></blockquote></div><br class=""><div class="">But those are two completely different use cases.</div><div class=""><br class=""></div><div class="">The fact that vendors (full disclosure - I work for Cisco) don’t want to</div><div class="">optimize for 64 bytes forwarding is totally independent on how those</div><div class="">architectures deal/manage to apply policies on the traffic.</div><div class=""><br class=""></div><div class="">64B traffic simply doesn’t happen apart from DDoS scenarios, so</div><div class="">why bother at all? Customers anyway want to use dedicated</div><div class="">anty-DDoS boxes, so apart from synthetic performance testing,</div><div class="">pushing the architecture to be able to forward couple of mpps more</div><div class="">just to cover the “64B” scenario means $ (sometimes $$$) just</div><div class="">to satisfy requirement that’s usually simply not there.</div><div class=""><br class=""></div><div class="">In other words, the fact that given architecture can’t forward "wire-rate"</div><div class="">of 64B traffic doesn’t mean that it can’t apply QoS for IMIX pattern</div><div class="">at wire-speed. Forwarding engine is usually different part of</div><div class="">hardware than services, more often than not decisions are totally</div><div class="">independent to speed up processing.</div><div class=""><br class=""></div><div class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">-- <br class="">Łukasz Bromirski<br class="">CCIE R&S/SP #15929, CCDE #2012::17, PGP Key ID: 0xFD077F6A</div></div></div></body></html>