From: Paul Chavent <Paul.Chavent@onera•fr>
To: Daniel Borkmann <dborkman@redhat•com>
Cc: Willem de Bruijn <willemb@google•com>,
Richard Cochran <richardcochran@gmail•com>,
Eric Dumazet <edumazet@google•com>,
daniel.borkmann@tik•ee.ethz.ch, xemul@parallels•com,
ebiederm@xmission•com, netdev@vger•kernel.org
Subject: Re: [PATCH] net-packet: tx timestamping on tpacket ring
Date: Mon, 15 Apr 2013 17:41:38 +0200 [thread overview]
Message-ID: <516C1FB2.50900@onera.fr> (raw)
In-Reply-To: <516A8A60.5020003@redhat.com>
On 04/14/2013 12:52 PM, Daniel Borkmann wrote:
> Paul, since you've reported / requested this, your use case would be to
> fill
> the ring, trigger a sendto() and then loop through all the frames to
> check the
> tx timestamps for your custom protocol mockup, then fill the returned
> frames
> again, etc.?
I've run a test that create (and setup) a tx ring buffer with 8 frames,
then fill the frames payload, then call sendto.
I've checked the timestamp by two means :
- check the timestamp in the tx ring after the status became
TP_STATUS_AVAILABLE again,
- by issuing 8 recvmsg on the ERRQUEUE.
Both timestamp are coherents and increment themselves.
The tests has been done with a UML kernel, and with software timestamps.
From my point of view, it seems usable.
However, I've found one strange behavior. I must call recvmsg as many
times as i have submitted a frame, or not at all. If i only pop the
ERRQUEUE for one or two message for instance, the next call to sentdo
fails with "No message of desired type" (errno 42).
Paul.
next prev parent reply other threads:[~2013-04-15 15:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 15:29 [RFC] net : add tx timestamp to packet mmap Paul Chavent
2012-12-12 19:23 ` David Miller
2012-12-13 7:13 ` Paul Chavent
2012-12-13 13:29 ` Richard Cochran
2012-12-13 16:13 ` Paul Chavent
2012-12-13 18:17 ` Richard Cochran
2012-12-14 7:57 ` Paul Chavent
2013-04-09 10:42 ` Paul Chavent
2013-04-09 13:15 ` Richard Cochran
2013-04-13 18:33 ` Willem de Bruijn
2013-04-13 18:56 ` [PATCH] net-packet: tx timestamping on tpacket ring Willem de Bruijn
2013-04-13 22:18 ` Daniel Borkmann
2013-04-13 22:47 ` David Miller
2013-04-14 0:04 ` Willem de Bruijn
2013-04-14 0:16 ` Willem de Bruijn
2013-04-14 0:49 ` Willem de Bruijn
2013-04-14 5:16 ` Daniel Borkmann
2013-04-14 0:00 ` Willem de Bruijn
2013-04-14 10:52 ` Daniel Borkmann
2013-04-14 13:07 ` Richard Cochran
2013-04-15 7:37 ` Paul Chavent
2013-04-15 16:56 ` Richard Cochran
2013-04-15 16:59 ` Willem de Bruijn
2013-04-17 10:22 ` Richard Cochran
2013-04-19 21:51 ` [PATCH net-next v2] packet: " Willem de Bruijn
2013-04-20 12:33 ` Daniel Borkmann
2013-04-21 2:30 ` Willem de Bruijn
2013-04-21 10:10 ` Daniel Borkmann
2013-04-21 16:42 ` Willem de Bruijn
2013-04-21 18:14 ` Daniel Borkmann
2013-04-22 8:19 ` Paul Chavent
2013-04-22 10:25 ` Daniel Borkmann
2013-04-22 14:23 ` Willem de Bruijn
2013-04-20 16:43 ` Richard Cochran
2013-04-21 2:34 ` Willem de Bruijn
2013-04-15 15:41 ` Paul Chavent [this message]
2013-04-15 9:45 ` [PATCH] net-packet: " David Laight
2013-04-15 17:08 ` Willem de Bruijn
2013-04-15 17:31 ` David Miller
2013-04-15 7:31 ` Paul Chavent
2013-04-15 16:37 ` 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=516C1FB2.50900@onera.fr \
--to=paul.chavent@onera$(echo .)fr \
--cc=daniel.borkmann@tik$(echo .)ee.ethz.ch \
--cc=dborkman@redhat$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=richardcochran@gmail$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=xemul@parallels$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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