From: Marcelo Ricardo Leitner <mleitner@redhat.com>
To: Shlomo Pongratz <shlomop@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: GRO aggregation
Date: Tue, 11 Sep 2012 15:48:13 -0300 [thread overview]
Message-ID: <504F876D.9020102@redhat.com> (raw)
In-Reply-To: <36F7E4A28C18BE4DB7C86058E7B607241E622015@MTRDAG01.mtl.com>
On 09/11/2012 03:41 PM, Shlomo Pongratz wrote:
> From: 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’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?
Actually it was an idea from top of my mind, I don't know how it applies
to ixgbe, sorry. But making the NIC hold the packets a bit more should
make it send larger ones to kernel. Trade-off between latency/throughput.
I was thinking about ethtool -c options, like rx-usecs*
Marcelo
next prev parent reply other threads:[~2012-09-11 18:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 13:45 GRO aggregation Shlomo Pongartz
2012-09-11 18:20 ` Marcelo Ricardo Leitner
2012-09-11 18:41 ` Shlomo Pongratz
2012-09-11 18:48 ` Marcelo Ricardo Leitner [this message]
2012-09-11 18:51 ` Shlomo Pongratz
2012-09-11 18:33 ` Eric Dumazet
2012-09-11 18:49 ` Shlomo Pongratz
2012-09-11 19:01 ` Eric Dumazet
2012-09-11 19:24 ` Shlomo Pongratz
2012-09-11 19:35 ` David Miller
2012-09-11 19:35 ` Eric Dumazet
2012-09-12 9:23 ` Shlomo Pongartz
2012-09-12 9:33 ` Eric Dumazet
2012-09-12 14:41 ` Shlomo Pongartz
2012-09-12 16:23 ` Rick Jones
2012-09-12 16:34 ` Shlomo Pongartz
2012-09-12 16:52 ` Rick Jones
2012-09-13 6:36 ` Shlomo Pongartz
2012-09-13 8:11 ` Eric Dumazet
2012-09-13 9:59 ` Or Gerlitz
2012-09-13 12:05 ` Eric Dumazet
2012-09-13 12:34 ` Eric Dumazet
2012-09-13 12:47 ` Or Gerlitz
2012-09-13 13:22 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504F876D.9020102@redhat.com \
--to=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shlomop@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.