From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shlomo Pongratz Subject: RE: GRO aggregation Date: Tue, 11 Sep 2012 18:41:49 +0000 Message-ID: <36F7E4A28C18BE4DB7C86058E7B607241E622015@MTRDAG01.mtl.com> References: <504F4063.9030706@mellanox.com>,<504F80DC.7010707@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "netdev@vger.kernel.org" To: "mleitner@redhat.com" Return-path: Received: from eu1sys200aog106.obsmtp.com ([207.126.144.121]:46423 "HELO eu1sys200aog106.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757737Ab2IKSly convert rfc822-to-8bit (ORCPT ); Tue, 11 Sep 2012 14:41:54 -0400 In-Reply-To: <504F80DC.7010707@redhat.com> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: =46rom: Marcelo Ricardo Leitner [mleitner@redhat.com] Sent: Tuesday, September 11, 2012 9:20 PM To: Shlomo Pongratz Cc: netdev@vger.kernel.org Subject: Re: GRO aggregation On 09/11/2012 10:45 AM, Shlomo Pongartz wrote: > Hi, > > I=92m checking GRO aggregation with kernel 3.6.0-rc1+ using Intel ixg= be > 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 tcpdum= p. > 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