From: Rick Jones <rick.jones2@hp•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: David Miller <davem@davemloft•net>,
netdev <netdev@vger•kernel.org>,
Or Gerlitz <ogerlitz@mellanox•com>,
Willem de Bruijn <willemb@google•com>
Subject: Re: [PATCH net-next] net: gro: add a per device gro flush timer
Date: Thu, 06 Nov 2014 08:42:59 -0800 [thread overview]
Message-ID: <545BA513.2070801@hp.com> (raw)
In-Reply-To: <1415241576.13896.62.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/05/2014 06:39 PM, Eric Dumazet wrote:
> On Wed, 2014-11-05 at 18:14 -0800, Eric Dumazet wrote:
>> On Wed, 2014-11-05 at 17:38 -0800, Rick Jones wrote:
>>
>>> Speaking of QPS, what happens to 200 TCP_RR tests when the feature is
>>> enabled?
>
> The possible reduction of QPS happens when you have a single flow like
> TCP_RR -- -r 40000,40000
>
> (Because we have one single TCP packet with 40000 bytes of payload,
> application is waked up once when Push flag is received)
>
> So cpu effiency is way better, but application has to copy 40000 bytes
> in one go _after_ Push flag, instead of being able to copy part of the
> data _before_ receiving the Push flag.
Thanks. That isn't too unlike what I've seen happen in the past with
say an 8K request size and switching back and forth between a 1500 and
9000 byte MTU.
happy benchmarking,
rick
next prev parent reply other threads:[~2014-11-06 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 0:55 [PATCH net-next] net: gro: add a per device gro flush timer Eric Dumazet
2014-11-06 1:38 ` Rick Jones
2014-11-06 2:14 ` Eric Dumazet
2014-11-06 2:39 ` Eric Dumazet
2014-11-06 16:42 ` Rick Jones [this message]
2014-11-06 21:25 ` David Miller
2014-11-06 22:11 ` Eric Dumazet
2014-11-07 3:36 ` David Miller
2014-11-07 4:15 ` Eric Dumazet
2014-11-07 5:09 ` [PATCH v2 net-next 1/2] " Eric Dumazet
2014-11-07 22:00 ` David Miller
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=545BA513.2070801@hp.com \
--to=rick.jones2@hp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=willemb@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox