From: Guy Harris <guy@alum.mit.edu>
To: jeffrey.t.kirsher@intel.com
Cc: Network Development <netdev@vger.kernel.org>,
Don Skidmore <donald.c.skidmore@intel.com>,
"Tantilov, Emil S" <emil.s.tantilov@intel.com>
Subject: Re: What ixgbe devices support HWTSTAMP_FILTER_ALL for hardware time stamping?
Date: Sat, 14 May 2016 11:55:11 -0700 [thread overview]
Message-ID: <42EB154F-A50F-4CB6-A8CD-06B7E61AA811@alum.mit.edu> (raw)
In-Reply-To: <1463211680.2720.5.camel@gmail.com>
On May 14, 2016, at 12:41 AM, Jeff Kirsher <tarbal@gmail.com> wrote:
> Are you planning to produce a patch or are you wanting us to do the work to
> fix the issue? Just asking so that work is not duplicated.
I'm willing to produce the patches, although
1) I don't currently have a platform set up to test whether they compile;
2) I don't have hardware on which to test whether they work (the person who submitted
https://github.com/the-tcpdump-group/tcpdump/issues/393#issuecomment-218442072
does, although he doesn't have X550 hardware - I guess he wants hardware time stamping on an 82599EB; it sounds as if that won't work, and his patch to the driver won't give him what he wants);
3) patches from the driver maintainers might 1) be more likely to do the right thing and 2) be more likely to be accepted.
prev parent reply other threads:[~2016-05-14 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 23:12 What ixgbe devices support HWTSTAMP_FILTER_ALL for hardware time stamping? Guy Harris
2016-05-14 2:23 ` Guy Harris
2016-05-14 7:30 ` Richard Cochran
2016-05-14 18:47 ` Guy Harris
2016-05-14 20:26 ` Richard Cochran
2016-05-15 2:11 ` Guy Harris
2016-05-15 7:51 ` Richard Cochran
2016-05-14 7:41 ` Jeff Kirsher
2016-05-14 18:55 ` Guy Harris [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=42EB154F-A50F-4CB6-A8CD-06B7E61AA811@alum.mit.edu \
--to=guy@alum.mit.edu \
--cc=donald.c.skidmore@intel.com \
--cc=emil.s.tantilov@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).