From: fklassen at appneta.com (Fred Klassen)
Subject: [PATCH net 0/4] Allow TX timestamp with UDP GSO
Date: Thu, 23 May 2019 14:06:47 -0700 [thread overview]
Message-ID: <20190523210651.80902-1-fklassen@appneta.com> (raw)
Fixes an issue where TX Timestamps are not arriving on the error queue
when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING.
Also this updates the UDP GSO selftests to optionally stress test
this condition, and report the reliability and performance of both
TX Timestamping and ZEROCOPY messages.
Fred Klassen (4):
net/udp_gso: Allow TX timestamp with UDP GSO
net/udpgso_bench_tx: options to exercise TX CMSG
net/udpgso_bench_tx: fix sendmmsg on unconnected socket
net/udpgso_bench_tx: audit error queue
net/ipv4/udp_offload.c | 4 +
tools/testing/selftests/net/udpgso_bench_tx.c | 376 ++++++++++++++++++++++++--
2 files changed, 358 insertions(+), 22 deletions(-)
--
2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: fklassen@appneta.com (Fred Klassen)
Subject: [PATCH net 0/4] Allow TX timestamp with UDP GSO
Date: Thu, 23 May 2019 14:06:47 -0700 [thread overview]
Message-ID: <20190523210651.80902-1-fklassen@appneta.com> (raw)
Message-ID: <20190523210647.F2vpWQosao00R5MpMeN_jEcvMWV209Yz0LtkXNw6xhM@z> (raw)
Fixes an issue where TX Timestamps are not arriving on the error queue
when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING.
Also this updates the UDP GSO selftests to optionally stress test
this condition, and report the reliability and performance of both
TX Timestamping and ZEROCOPY messages.
Fred Klassen (4):
net/udp_gso: Allow TX timestamp with UDP GSO
net/udpgso_bench_tx: options to exercise TX CMSG
net/udpgso_bench_tx: fix sendmmsg on unconnected socket
net/udpgso_bench_tx: audit error queue
net/ipv4/udp_offload.c | 4 +
tools/testing/selftests/net/udpgso_bench_tx.c | 376 ++++++++++++++++++++++++--
2 files changed, 358 insertions(+), 22 deletions(-)
--
2.11.0
next reply other threads:[~2019-05-23 21:06 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 21:06 fklassen [this message]
2019-05-23 21:06 ` [PATCH net 0/4] Allow TX timestamp with UDP GSO Fred Klassen
2019-05-23 21:06 ` [PATCH net 1/4] net/udp_gso: " fklassen
2019-05-23 21:06 ` Fred Klassen
2019-05-23 21:39 ` willemdebruijn.kernel
2019-05-23 21:39 ` Willem de Bruijn
2019-05-24 1:38 ` fklassen
2019-05-24 1:38 ` Fred Klassen
2019-05-24 4:53 ` willemdebruijn.kernel
2019-05-24 4:53 ` Willem de Bruijn
2019-05-24 16:34 ` fklassen
2019-05-24 16:34 ` Fred Klassen
2019-05-24 19:29 ` willemdebruijn.kernel
2019-05-24 19:29 ` Willem de Bruijn
2019-05-24 22:01 ` fklassen
2019-05-24 22:01 ` Fred Klassen
2019-05-25 15:20 ` willemdebruijn.kernel
2019-05-25 15:20 ` Willem de Bruijn
2019-05-25 18:47 ` fklassen
2019-05-25 18:47 ` Fred Klassen
2019-05-27 1:30 ` willemdebruijn.kernel
2019-05-27 1:30 ` Willem de Bruijn
2019-05-27 2:09 ` willemdebruijn.kernel
2019-05-27 2:09 ` Willem de Bruijn
2019-05-25 20:46 ` fklassen
2019-05-25 20:46 ` Fred Klassen
2019-05-23 21:59 ` willemdebruijn.kernel
2019-05-23 21:59 ` Willem de Bruijn
2019-05-25 20:09 ` fklassen
2019-05-25 20:09 ` Fred Klassen
2019-05-25 20:47 ` fklassen
2019-05-25 20:47 ` Fred Klassen
2019-05-23 21:06 ` [PATCH net 2/4] net/udpgso_bench_tx: options to exercise TX CMSG fklassen
2019-05-23 21:06 ` Fred Klassen
2019-05-23 21:45 ` willemdebruijn.kernel
2019-05-23 21:45 ` Willem de Bruijn
2019-05-23 21:52 ` willemdebruijn.kernel
2019-05-23 21:52 ` Willem de Bruijn
2019-05-24 2:10 ` fklassen
2019-05-24 2:10 ` Fred Klassen
2019-05-23 21:06 ` [PATCH net 3/4] net/udpgso_bench_tx: fix sendmmsg on unconnected socket fklassen
2019-05-23 21:06 ` Fred Klassen
2019-05-23 21:06 ` [PATCH net 4/4] net/udpgso_bench_tx: audit error queue fklassen
2019-05-23 21:06 ` Fred Klassen
2019-05-23 21:56 ` willemdebruijn.kernel
2019-05-23 21:56 ` Willem de Bruijn
2019-05-24 1:27 ` fklassen
2019-05-24 1:27 ` Fred Klassen
2019-05-24 5:02 ` willemdebruijn.kernel
2019-05-24 5:02 ` Willem de Bruijn
2019-05-27 21:30 ` fklassen
2019-05-27 21:30 ` Fred Klassen
2019-05-27 21:46 ` willemdebruijn.kernel
2019-05-27 21:46 ` Willem de Bruijn
2019-05-27 22:56 ` fklassen
2019-05-27 22:56 ` Fred Klassen
2019-05-28 1:15 ` willemdebruijn.kernel
2019-05-28 1:15 ` Willem de Bruijn
2019-05-28 5:19 ` fklassen
2019-05-28 5:19 ` Fred Klassen
2019-05-28 15:08 ` willemdebruijn.kernel
2019-05-28 15:08 ` Willem de Bruijn
2019-05-28 16:57 ` fklassen
2019-05-28 16:57 ` Fred Klassen
2019-05-28 17:07 ` willemdebruijn.kernel
2019-05-28 17:07 ` Willem de Bruijn
2019-05-28 17:11 ` willemdebruijn.kernel
2019-05-28 17:11 ` Willem de Bruijn
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=20190523210651.80902-1-fklassen@appneta.com \
--to=linux-kselftest@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