From: Mike Maloney <maloneykernel@gmail.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: willemdebruijn.kernel@gmail.com, soheil@google.com,
Mike Maloney <maloney@google.com>
Subject: [PATCH v2 net-next 0/2] Add software rx timestamp for TCP.
Date: Tue, 22 Aug 2017 17:08:47 -0400 [thread overview]
Message-ID: <20170822210849.23162-1-maloneykernel@gmail.com> (raw)
From: Mike Maloney <maloney@google.com>
Add software rx timestamps for TCP, and a test to ensure consistency of
behavior between IP, UDP, and TCP implementation.
Changes since v1:
-Initialize tss->ts[1] to 0 if caller requested any timestamps.
-Fix test case to validate that tss->ts[1] is zero.
-Fix tests to actually use a raw socket.
-Fix --tcp flag to work on the test.
Mike Maloney (2):
tcp: Extend SOF_TIMESTAMPING_RX_SOFTWARE to TCP recvmsg
selftests/net: Add a test to validate behavior of rx timestamps
include/net/tcp.h | 9 +-
net/ipv4/tcp.c | 65 ++++
net/ipv4/tcp_input.c | 35 +-
net/ipv4/tcp_ipv4.c | 2 +
net/ipv6/tcp_ipv6.c | 2 +
.../selftests/networking/timestamping/.gitignore | 1 +
.../selftests/networking/timestamping/Makefile | 4 +-
.../networking/timestamping/rxtimestamp.c | 389 +++++++++++++++++++++
8 files changed, 501 insertions(+), 6 deletions(-)
create mode 100644 tools/testing/selftests/networking/timestamping/rxtimestamp.c
--
2.14.1.480.gb18f417b89-goog
next reply other threads:[~2017-08-22 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 21:08 Mike Maloney [this message]
2017-08-22 21:08 ` [PATCH v2 net-next 1/2] tcp: Extend SOF_TIMESTAMPING_RX_SOFTWARE to TCP recvmsg Mike Maloney
2017-08-22 21:32 ` Willem de Bruijn
2017-08-22 21:08 ` [PATCH v2 net-next 2/2] selftests/net: Add a test to validate behavior of rx timestamps Mike Maloney
2017-08-22 21:39 ` Willem de Bruijn
2017-08-24 3:32 ` [PATCH v2 net-next 0/2] Add software rx timestamp for TCP 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=20170822210849.23162-1-maloneykernel@gmail.com \
--to=maloneykernel@gmail.com \
--cc=davem@davemloft.net \
--cc=maloney@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@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;
as well as URLs for NNTP newsgroup(s).