From: Willem de Bruijn <willemb@google.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, richardcochran@gmail.com,
eric.dumazet@gmail.com, luto@amacapital.net,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next RFC 0/5] net-timestamp: address blinding and batching
Date: Fri, 9 Jan 2015 12:31:54 -0500 [thread overview]
Message-ID: <1420824719-28848-1-git-send-email-willemb@google.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Two issues were raised during recent timestamping discussions:
1. looping full packets on the error queue exposes packet headers
2. TCP timestamping with retransmissions generates many timestamps
This RFC patchset is an attempt at addressing both without breaking
legacy behavior.
Patch 1 reintroduces the "no payload" timestamp option, which loops
timestamps onto an empty skb. Patch 2 then gives administrators the
power to block all timestamp requests by unprivileged users that
contain data. I proposed this earlier as a backward compatible
workaround in the discussion of
net-timestamp: pull headers for SOCK_STREAM
http://patchwork.ozlabs.org/patch/414810/
Patch 3 only updates the txtimestamp example to test this option.
When looping timestamps without data, there is no need to associate
a timestamp with a specific packet. Patch 4 loops multiple timestamps
onto a single outstanding packet if this has no payload. It is a
variant of the cookies approach that David proposed in
net-timestamp: TCP timestamping
http://patchwork.ozlabs.org/patch/376513/
That patch turns out to introduce a quite a bit of code to save
relatively few bytes because
1. no-payload already limits the per-skb size that is queued and
2. batching is limited by send() failing as soon as there is an
outstanding packet on the error queue. Therefore, I'm fine
with dropping this. By now, it is at least recorded in patchwork.
Patch 5, finally, creates a new short SO_TIMESTAMPING option,
SOF_TIMESTAMPING_TX, that combines all recent options, as a push
to get future applications to use the new ID and no-payload based
API by default.
Willem de Bruijn (5):
net-timestamp: no-payload option
net-timestamp: no-payload only sysctl
net-timestamp: no-payload option in txtimestamp test
net-timestamp: tx timestamp cookies
net-timestamp: tx timestamping default mode flag
.../networking/timestamping/txtimestamp.c | 28 ++++-
include/linux/skbuff.h | 12 ++
include/net/sock.h | 4 +-
include/uapi/linux/errqueue.h | 1 +
include/uapi/linux/net_tstamp.h | 11 +-
net/core/skbuff.c | 134 ++++++++++++++++++---
net/core/sock.c | 3 +
net/core/sysctl_net_core.c | 9 ++
net/ipv4/ip_sockglue.c | 9 +-
net/ipv6/datagram.c | 4 +-
net/rxrpc/ar-error.c | 5 +
net/socket.c | 64 +++++++++-
12 files changed, 250 insertions(+), 34 deletions(-)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-01-09 17:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 17:31 Willem de Bruijn [this message]
2015-01-09 17:31 ` [PATCH net-next RFC 1/5] net-timestamp: no-payload option Willem de Bruijn
2015-01-09 19:43 ` Andy Lutomirski
2015-01-09 19:47 ` Willem de Bruijn
2015-01-09 20:02 ` Andy Lutomirski
2015-01-09 20:33 ` Willem de Bruijn
2015-01-09 20:55 ` Andy Lutomirski
2015-01-09 21:18 ` Willem de Bruijn
2015-01-09 22:00 ` Andy Lutomirski
2015-01-11 20:26 ` Richard Cochran
2015-01-15 18:22 ` Willem de Bruijn
2015-01-09 17:31 ` [PATCH net-next RFC 2/5] net-timestamp: no-payload only sysctl Willem de Bruijn
2015-01-09 17:31 ` [PATCH net-next RFC 3/5] net-timestamp: no-payload option in txtimestamp test Willem de Bruijn
2015-01-09 17:31 ` [PATCH net-next RFC 4/5] net-timestamp: tx timestamp cookies Willem de Bruijn
2015-01-09 17:31 ` [PATCH net-next RFC 5/5] net-timestamp: tx timestamping default mode flag Willem de Bruijn
2015-01-11 20:32 ` Richard Cochran
2015-01-12 1:49 ` Willem de Bruijn
2015-01-12 8:26 ` Richard Cochran
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=1420824719-28848-1-git-send-email-willemb@google.com \
--to=willemb@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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).