All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Zimmermann <madroach@zakweb.de>
To: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: SO_TIMESTAMPING fix and design decisions
Date: Sun, 20 Sep 2009 09:52:42 +0200	[thread overview]
Message-ID: <20090920095242.5cd42f1a@pundit> (raw)
In-Reply-To: <1253398161.14869.2.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Sat, 19 Sep 2009 15:09:21 -0700
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com> wrote:

> > hardware timestamps only work for the Intel igb driver. I have 
> > access to two test machines with NICs supported by this driver.
> 
> Intel's 82599, supported by ixgbe, also has the same IEEE 1588
> timestamping support in hardware.  We haven't implemented the support
> yet in ixgbe, but the hardware is there and does work.  If you were
> curious of the interface, the datasheet for the hardware is available on
> our SourceForge site (e1000.sf.net).

hi! thanks for the reply.

I already got the documentation for the 82576 cards I have access to. I 
won't be able to afford another pair.

What do you think about my idea to expose the relevant registers to 
userspace? I believe it would not be too difficult for userspace to 
configure the timestamps this way and would allow way more flexibility. 
Of course I would #DEFINE the constants used to set the registers.

Christopher Zimmermann

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-20  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 17:25 SO_TIMESTAMPING fix and design decisions Christopher Zimmermann
2009-09-19 22:09 ` Peter P Waskiewicz Jr
2009-09-20  7:52   ` Christopher Zimmermann [this message]
2009-09-20 17:48     ` Peter P Waskiewicz Jr
2009-09-20 18:50       ` Christopher Zimmermann
2009-09-21 17:59         ` John Ronciak

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=20090920095242.5cd42f1a@pundit \
    --to=madroach@zakweb.de \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@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 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.