[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1724483B@AcuExch.aculab.com>
Date: Wed, 14 May 2014 14:28:24 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Jesper Dangaard Brouer' <brouer@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Alexander Duyck <alexander.h.duyck@...el.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Daniel Borkmann <dborkman@...hat.com>,
"Florian Westphal" <fw@...len.de>,
"David S. Miller" <davem@...emloft.net>,
"Stephen Hemminger" <shemminger@...tta.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Robert Olsson <robert@...julf.se>,
Ben Greear <greearb@...delatech.com>,
John Fastabend <john.r.fastabend@...el.com>,
"danieltt@....se" <danieltt@....se>,
"zhouzhouyi@...il.com" <zhouzhouyi@...il.com>
Subject: RE: [net-next PATCH 2/5] ixgbe: increase default TX ring buffer to
1024
From: Jesper Dangaard Brouer
> Using pktgen I'm seeing the ixgbe driver "push-back", due TX ring
> running full. Thus, the TX ring is artificially limiting pktgen.
>
> Diagnose via "ethtool -S", look for "tx_restart_queue" or "tx_busy"
> counters.
Have you tried reducing the tx interrupt mitigation delay.
It might just be that the end of tx interrupt is delayed too long.
David
Powered by blists - more mailing lists