From: Michael Chan <mc...@broadcom.com> Date: Sat, 2 Jan 2016 23:44:57 -0500
> The bnxt hardware uses a completion ring for rx and tx events. The driver > has to process the completion ring entries sequentially for the events. > The current code only supports an rx/tx ring pair for each completion ring. > This patch series add support for using a dedicated completion ring for > rx only or tx only as an option configuarble using ethtool -L. > > The benefits for using dedicated completion rings are: > > 1. A burst of rx packets can cause delay in processing tx events if the > completion ring is shared. If tx queue is stopped by BQL, this can cause > delay in re-starting the tx queue. > > 2. A completion ring is sized according to the rx and tx ring size rounded > up to the nearest power of 2. When the completion ring is shared, it is > sized by adding the rx and tx ring sizes and then rounded to the next power > of 2, often with a lot of wasted space. > > 3. Using dedicated completion ring, we can adjust the tx and rx coalescing > parameters independently for rx and tx. Series applied, thanks Michael. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
