From: Oliver Hartkopp <oliver@hartkopp.net>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: TX time stamping
Date: Mon, 30 Mar 2009 20:09:40 +0200 [thread overview]
Message-ID: <49D10AE4.8070907@hartkopp.net> (raw)
In-Reply-To: <1238081410.19066.125.camel@ecld0pohly>
Patrick Ohly wrote:
> On Thu, 2009-03-26 at 14:48 +0000, Herbert Xu wrote:
>> On Wed, Mar 25, 2009 at 08:08:44AM +0100, Patrick Ohly wrote:
>>> I suggest to make it so that the sender gets the packet back once per
>>> interface, with different time stamps and information about the
>>> interface.
>> That could be awkward. What if the second or subsequent instance
>> of the packet is held up indefinitely?
>
> The sender must be prepared for packet loss anyway (for example, during
> stress tests I have seen that packets were dropped between socket layer
> and device driver).
>
> Getting a TX time stamp only for some, but not all expected interfaces,
> or getting some results much later isn't that different.
>
> After a certain timeout the sender must assume that the packet was lost
> and resend. An unexpected response for a packet that was supposed to be
> lost must be ignored.
>
Hello Patrick,
i wonder if using the IP stack for PTP with the possibility to send TX-stamped
PDUs on various interfaces is the best solution.
I'm not aware of all the routing, packet scheduling, etc. stuff that much -
but does it probably make sense to use AF_PACKET for PTP, where you can
specify the interface and build a PTP IP PDU directly? I assume this does not
make that big difference to the ptpd in userspace.
Any ideas? Or am i completely wrong here?
Regards,
Oliver
next prev parent reply other threads:[~2009-03-30 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 18:31 TX time stamping Patrick Ohly
2009-03-19 21:05 ` David Miller
2009-03-20 2:10 ` Herbert Xu
2009-03-25 7:08 ` Patrick Ohly
2009-03-26 14:48 ` Herbert Xu
2009-03-26 15:30 ` Patrick Ohly
2009-03-30 18:09 ` Oliver Hartkopp [this message]
2009-03-31 6:53 ` Patrick Ohly
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=49D10AE4.8070907@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=patrick.ohly@intel.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).