All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Guy Harris <guy@alum.mit.edu>
Cc: Network Development <netdev@vger.kernel.org>
Subject: Re: What ixgbe devices support HWTSTAMP_FILTER_ALL for hardware time stamping?
Date: Sat, 14 May 2016 22:26:53 +0200	[thread overview]
Message-ID: <20160514202653.GA6529@netboy> (raw)
In-Reply-To: <4AAA3CE1-B137-4AC1-AB85-B4690E8E3E12@alum.mit.edu>

On Sat, May 14, 2016 at 11:47:22AM -0700, Guy Harris wrote:
> So if you have a GUI application for packet capture, with a combo box to select the type of time stamping, should it:
> 
> 	1) regardless of whether ETHTOOL_GET_TS_INFO is available, open the adapter, try each of the time stamp types to see whether it works, and show a combo box based on that;
> 
> 	2) use ETHTOOL_GET_TS_INFO if available;
> 
> 	3) offer all possibilities regardless of whether they work with the adapter or not, and just report an error for possibilities that don't work?
> 
> My preference is 2) - which is the main reason why libpcap offers "what possibilities are available?" APIs, not just "request this possibility" APIs.

You are going to have to implement #1 in any case, if you want your
program to work on all kernels.  IIRC get_ts_info appeared in 3.5.

Thanks,
Richard

  reply	other threads:[~2016-05-14 20:26 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 [this message]
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

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=20160514202653.GA6529@netboy \
    --to=richardcochran@gmail.com \
    --cc=guy@alum.mit.edu \
    --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 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.