Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: netdev@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] NET : Adding SO_TIMESTAMPNS / SCM_TIMESTAMPNS support
Date: Fri, 09 Mar 2007 14:17:24 -0800 (PST)	[thread overview]
Message-ID: <20070309.141724.112850583.davem@davemloft.net> (raw)
In-Reply-To: <200703091939.42656.dada1@cosmosbay.com>

From: Eric Dumazet <dada1@cosmosbay.com>
Date: Fri, 9 Mar 2007 19:39:42 +0100

> [PATCH] NET : Adding SO_TIMESTAMPNS / SCM_TIMESTAMPNS support
> 
> Now that network timestamps use ktime_t infrastructure, we can add a new 
> SOL_SOCKET sockopt  SO_TIMESTAMPNS.
> 
> This command is similar to SO_TIMESTAMP, but permits transmission of 
> a 'timespec struct' instead of a 'timeval struct' control message. 
> (nanosecond resolution instead of microsecond)
> 
> Control message is labelled SCM_TIMESTAMPNS instead of SCM_TIMESTAMP
> 
> A socket cannot mix SO_TIMESTAMP and SO_TIMESTAMPNS : the two modes are 
> mutually exclusive.
> 
> sock_recv_timestamp() became too big to be fully inlined so I added a 
> __sock_recv_timestamp() helper function.
> 
> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
> CC: linux-arch@vger.kernel.org
> 

Applied, thanks for following up on all of this nanosecond
timestamp work.

      reply	other threads:[~2007-03-09 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45E6F744.8070106@linux-foundation.org>
     [not found] ` <200703021538.41284.dada1@cosmosbay.com>
     [not found]   ` <200703081517.57539.dada1@cosmosbay.com>
2007-03-09  4:39     ` [PATCH] NET : Introduce SIOCGSTAMPNS ioctl to get timestamps with nanosec resolution David Miller
2007-03-09 18:39     ` [PATCH] NET : Adding SO_TIMESTAMPNS / SCM_TIMESTAMPNS support Eric Dumazet
2007-03-09 22:17       ` David Miller [this message]

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=20070309.141724.112850583.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dada1@cosmosbay.com \
    --cc=linux-arch@vger.kernel.org \
    --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