From: David Miller <davem@davemloft.net>
To: willemdebruijn.kernel@gmail.com
Cc: fklassen@appneta.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
willemb@google.com
Subject: Re: [PATCH net-next v3 0/3] UDP GSO audit tests
Date: Mon, 17 Jun 2019 16:30:50 -0700 (PDT) [thread overview]
Message-ID: <20190617.163050.1853001451258961153.davem@davemloft.net> (raw)
In-Reply-To: <CAF=yD-KQ1dxmNbR8-xoiNTfwHXzO-wQRpz+0ZFN9o36+UE_e6A@mail.gmail.com>
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: Mon, 17 Jun 2019 16:29:37 -0400
> On Mon, Jun 17, 2019 at 3:09 PM Fred Klassen <fklassen@appneta.com> wrote:
>>
>> Updates to UDP GSO selftests ot optionally stress test CMSG
>> subsytem, and report the reliability and performance of both
>> TX Timestamping and ZEROCOPY messages.
>>
>> Fred Klassen (3):
>> net/udpgso_bench_tx: options to exercise TX CMSG
>> net/udpgso_bench.sh add UDP GSO audit tests
>> net/udpgso_bench.sh test fails on error
>>
>> tools/testing/selftests/net/udpgso_bench.sh | 52 ++++-
>> tools/testing/selftests/net/udpgso_bench_tx.c | 291 ++++++++++++++++++++++++--
>> 2 files changed, 327 insertions(+), 16 deletions(-)
>>
>> --
>
> For the series:
>
> Acked-by: Willem de Bruijn <willemb@google.com>
Series applied, thanks everyone.
prev parent reply other threads:[~2019-06-17 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 19:08 [PATCH net-next v3 0/3] UDP GSO audit tests Fred Klassen
2019-06-17 19:08 ` [PATCH net-next v3 1/3] net/udpgso_bench_tx: options to exercise TX CMSG Fred Klassen
2019-06-17 19:08 ` [PATCH net-next v3 2/3] net/udpgso_bench.sh add UDP GSO audit tests Fred Klassen
2019-06-17 19:08 ` [PATCH net-next v3 3/3] net/udpgso_bench.sh test fails on error Fred Klassen
2019-06-17 20:29 ` [PATCH net-next v3 0/3] UDP GSO audit tests Willem de Bruijn
2019-06-17 23:30 ` David Miller [this message]
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=20190617.163050.1853001451258961153.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fklassen@appneta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox