On Tue, Mar 29, 2016 at 09:54:18AM -0700, Stephen Hemminger wrote:
> On Tue, 29 Mar 2016 10:31:19 +0100
> Bruce Richardson wrote:
>
> > On Mon, Mar 28, 2016 at 06:45:26PM -0700, Mohammad El-Shabani wrote:
> > > Hi,
> > > Looking into why it hurts performance, I see that ixgbe_dev_rx_queue_count
On Mon, Mar 28, 2016 at 06:45:26PM -0700, Mohammad El-Shabani wrote:
> Hi,
> Looking into why it hurts performance, I see that ixgbe_dev_rx_queue_count
> is implemented a scan of elements of rx descriptors, which is very
> expensive. I am wondering why its implemented the way it is. Could it not
>
On Tue, 29 Mar 2016 10:31:19 +0100
Bruce Richardson wrote:
> On Mon, Mar 28, 2016 at 06:45:26PM -0700, Mohammad El-Shabani wrote:
> > Hi,
> > Looking into why it hurts performance, I see that ixgbe_dev_rx_queue_count
> > is implemented a scan of elements of rx descriptors, which is very
> >
Hi Mohammad,
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Mohammad El-Shabani
> Sent: Tuesday, March 29, 2016 9:45 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] librte_pmd_ixgbe implementation of
> ixgbe_dev_rx_queue_count
>
>
Hi,
Looking into why it hurts performance, I see that ixgbe_dev_rx_queue_count
is implemented a scan of elements of rx descriptors, which is very
expensive. I am wondering why its implemented the way it is. Could it not
just read the head location from the driver?
Thanks!
Mohammad El-Shabani
5 matches
Mail list logo
