All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org
Subject: Re: [rfc] new sk_buff member: hwstamp
Date: Mon, 14 Jul 2008 17:43:21 -0700	[thread overview]
Message-ID: <20080714174321.30d6d62a@extreme> (raw)
In-Reply-To: <200807141843.00845.opurdila@ixiacom.com>

On Mon, 14 Jul 2008 18:43:00 +0300
Octavian Purdila <opurdila@ixiacom.com> wrote:

> 
> Hi everybody,
> 
> In our Linux port we added a new sk_buff member, hwstamp, to store a hardware 
> generated timestamp for received packets. The hardware can also insert  
> hardware timestamps in the payload on the TX path and can have the RX / TX 
> clocks synchronized. We use this infrastructure to compute one-way delays 
> with high precision (20ns resolution).
> 
> I know that adding new members to such heavily used structures like the skb is 
> viewed harshly - especially for such exotic cases as the one described above. 
> So, would such a patch be considered for inclusion? Or maybe there is a 
> better way of doing the above?
> 

Why not do some clock synchronization and use existing absolute timestamp?
This would benefit system generally since it would give more accurate values
for network traffic analysis.

  parent reply	other threads:[~2008-07-15  0:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 15:43 [rfc] new sk_buff member: hwstamp Octavian Purdila
2008-07-14 17:25 ` Andi Kleen
2008-07-14 17:57   ` Oliver Hartkopp
2008-07-14 18:30     ` Octavian Purdila
2008-07-14 18:58       ` Oliver Hartkopp
2008-07-14 20:07         ` Octavian Purdila
2008-07-14 18:49   ` Octavian Purdila
2008-07-15  0:43 ` Stephen Hemminger [this message]
2008-07-15 10:39   ` Octavian Purdila

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=20080714174321.30d6d62a@extreme \
    --to=shemminger@vyatta.com \
    --cc=netdev@vger.kernel.org \
    --cc=opurdila@ixiacom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.