From: Eric Dumazet <eric.dumazet@gmail.com>
To: Edward Cree <ecree@solarflare.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
davem@davemloft.net
Cc: linux-net-drivers@solarflare.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 3/4] net: make listified RX functions return number of good packets
Date: Fri, 7 Sep 2018 04:43:09 -0700 [thread overview]
Message-ID: <f45bde72-e02e-dc5f-45ad-b98ceb189b6a@gmail.com> (raw)
In-Reply-To: <e184f2c1-fe28-ad6e-460d-950d8a363852@solarflare.com>
On 09/07/2018 03:44 AM, Edward Cree wrote:
>
> Any suggestions on how to construct a test that will?
>
Say 50 concurrent netperf -t TCP_RR -- -r 8000,8000
This way you have a mix of GRO-candidates, and non GRO ones (pure acks)
GRO sizes would be reasonable (not full size GRO packets).
next prev parent reply other threads:[~2018-09-07 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 14:24 [PATCH v2 net-next 0/4] net: batched receive in GRO path Edward Cree
2018-09-06 14:26 ` [PATCH v2 net-next 1/4] net: introduce list entry point for GRO Edward Cree
2018-09-06 14:26 ` [PATCH v2 net-next 2/4] sfc: use batched receive " Edward Cree
2018-09-06 14:26 ` [PATCH v2 net-next 3/4] net: make listified RX functions return number of good packets Edward Cree
2018-09-07 2:27 ` Eric Dumazet
2018-09-07 10:44 ` Edward Cree
2018-09-07 11:43 ` Eric Dumazet [this message]
2018-09-06 14:26 ` [PATCH v2 net-next 4/4] net/core: handle GRO_NORMAL skbs as a list in napi_gro_receive_list Edward Cree
2018-09-07 2:32 ` [PATCH v2 net-next 0/4] net: batched receive in GRO path Eric Dumazet
2018-09-07 10:51 ` Edward Cree
2018-09-11 18:34 ` Edward Cree
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=f45bde72-e02e-dc5f-45ad-b98ceb189b6a@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).