From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ingo Kofler <ikofler@edu.uni-klu.ac.at>
Cc: netdev@vger.kernel.org
Subject: Re: Problems obtaining software TX timestamps
Date: Wed, 08 Sep 2010 17:12:51 +0200 [thread overview]
Message-ID: <1283958771.2748.85.camel@edumazet-laptop> (raw)
In-Reply-To: <4C877D8A.6040002@edu.uni-klu.ac.at>
Le mercredi 08 septembre 2010 à 14:11 +0200, Ingo Kofler a écrit :
> Dear all,
>
> I am trying to obtain software TX timestamps for a each outgoing packet
> of an UDP socket. For that purpose I set the SO_TIMESTAMPING socket
> option to SOF_TIMESTAMPING_TX_SOFTWARE | SOF_TIMESTAMPING_SOFTWARE. The
> setsockopt call succeeds and also a subsequent getsockopt returns the
> correct flags. However, if a send a single datagram over the socket and
> try to fetch the packet as well as its timestamp via the socket's
> MSG_ERRQUEUE I do not get any information. Rather, the select call waits
> infinitely on the error queue....
>
> I hardly found any documentation on this timestamping mechanism except
> the text file in the kernel source code. All I've figured out is that if
> I want to have hardware TX timestamps, I'll have to make a further ioctl
> which requires root permissions to active the hardware timestamping. But
> this is not what I want... software timestamps are sufficient for me.
To my knowledge, no driver calls skb_tx_timestamp()
You'll need to tweak your NIC driver to play with this TX timestamps
next prev parent reply other threads:[~2010-09-08 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 12:11 Problems obtaining software TX timestamps Ingo Kofler
2010-09-08 15:12 ` Eric Dumazet [this message]
2010-09-08 21:21 ` Ingo Kofler
2010-09-08 21:24 ` David Miller
2010-09-09 6:35 ` Richard Cochran
2010-09-09 8:26 ` Ingo Kofler
2010-09-09 13:57 ` Richard Cochran
2010-09-09 14:02 ` Eric Dumazet
2010-09-09 14:31 ` Loke, Chetan
2010-09-09 17:32 ` Richard Cochran
2010-09-09 18:58 ` Eric Dumazet
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=1283958771.2748.85.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=ikofler@edu.uni-klu.ac.at \
--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