[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36F7E4A28C18BE4DB7C86058E7B607241E622015@MTRDAG01.mtl.com>
Date: Tue, 11 Sep 2012 18:41:49 +0000
From: Shlomo Pongratz <shlomop@...lanox.com>
To: "mleitner@...hat.com" <mleitner@...hat.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: GRO aggregation
From: Marcelo Ricardo Leitner [mleitner@...hat.com]
Sent: Tuesday, September 11, 2012 9:20 PM
To: Shlomo Pongratz
Cc: netdev@...r.kernel.org
Subject: Re: GRO aggregation
On 09/11/2012 10:45 AM, Shlomo Pongartz wrote:
> Hi,
>
> I’m checking GRO aggregation with kernel 3.6.0-rc1+ using Intel ixgbe
> driver.
> The mtu is 1500 and GRO is on and so are SG and RX checksum.
> I ran iperf with default setting and monitor the receiver with tcpdump.
> The tcpdump shows that the maximal aggregation is 32120 which is 21 * 1500.
> In the transmitter side tcpdump shows that TSO works better (~64K).
> I did a capture without GRO enabled to see if there was a difference
> between any flag
> of any two consecutive packets that forced flushing but didn't find
> anything.
> Is the GRO aggregation can be tuned.
Hi Shlomo,
Have you tried tuning coalescing parameters?
Marcelo
Hi Marcelo
I didn't play with interrupts coalescing.
Do you suggest to increase the value?
Shlomo--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists