From: Richard Cochran <richardcochran@gmail.com>
To: <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH net-next 0/2] Transmit time stamping on tun/tap interfaces
Date: Fri, 19 Jul 2013 19:40:08 +0200 [thread overview]
Message-ID: <cover.1374254757.git.richardcochran@gmail.com> (raw)
This series adds transmit SO_TIMESTAMPING for tun and tap devices.
Having this support is useful for testing multiple instances of PTP
programs (for example, to exercise the best master clock behavior)
and for synchronizing virtual guests.
The first patch refactors the code that delivers raw error queue
packets into a common function, in order to avoid multiple, nearly
identical implementations. This can be used whenever a network layer
has an error queue for transmit time stamp reporting only.
Thanks,
Richard
Richard Cochran (2):
Provide a generic socket error queue delivery method for Tx time
stamps.
tun: Support software transmit time stamping.
drivers/net/tun.c | 14 +++++++++++--
include/net/sock.h | 2 ++
include/uapi/linux/if_tun.h | 3 +++
net/core/sock.c | 47 ++++++++++++++++++++++++++++++++++++++++++
net/packet/af_packet.c | 48 ++-----------------------------------------
5 files changed, 66 insertions(+), 48 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-07-19 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 17:40 Richard Cochran [this message]
2013-07-19 17:40 ` [PATCH net-next 1/2] Provide a generic socket error queue delivery method for Tx time stamps Richard Cochran
2013-07-19 17:40 ` [PATCH net-next 2/2] tun: Support software transmit time stamping Richard Cochran
2013-07-22 21:59 ` [PATCH net-next 0/2] Transmit time stamping on tun/tap interfaces 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=cover.1374254757.git.richardcochran@gmail.com \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=mst@redhat.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).