All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: "Mintz, Yuval" <Yuval.Mintz@cavium.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
	"Kalluru, Sudarsana" <Sudarsana.Kalluru@cavium.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 2/2] qede: Add driver support for PTP.
Date: Tue, 31 Jan 2017 18:43:27 +0100	[thread overview]
Message-ID: <20170131174327.GA21731@localhost.localdomain> (raw)
In-Reply-To: <BL2PR07MB23069DF93C3944BAB27F807F8D4A0@BL2PR07MB2306.namprd07.prod.outlook.com>

On Tue, Jan 31, 2017 at 03:08:11PM +0000, Mintz, Yuval wrote:
> While it surely answers my question, I still don't think of an event
> reoccurring 16 times a second as optimization-crucial.
> Is there any reasonable scenario where the interval is
> significantly smaller, or is it merely some theoretical specification?

Its theoretical, like ipv6 addresses.

> [I'd like to see the machine that can handle the 2^(-128) sec interval]

;)
 
> Again, I don't see how we can achieve that given that qede has to check
> Its internal state to check whether it's right to utilize the ptp-related hw
> configurations and only then call the qed function. As qed can't do it for
> qede, we can't directly map qed's function into the ptp_clock_info,
> but rather have to call it after taking qede's state-lock.

Fair enough.

Thanks,
Richard

  reply	other threads:[~2017-01-31 17:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29  7:28 [PATCH net-next v2 0/2] qed*: Add support for PTP Sudarsana Kalluru
2017-01-29  7:28 ` [PATCH net-next v2 1/2] qed: Add infrastructure for PTP support Sudarsana Kalluru
2017-01-29  8:32   ` kbuild test robot
2017-01-29 15:28   ` Richard Cochran
2017-01-29 15:31   ` Richard Cochran
2017-01-29 17:26     ` Mintz, Yuval
2017-01-29 20:51       ` Richard Cochran
2017-01-29 21:36         ` Mintz, Yuval
2017-01-30 13:26           ` Richard Cochran
2017-01-30 18:00             ` Mintz, Yuval
2017-01-29  7:28 ` [PATCH net-next v2 2/2] qede: Add driver support for PTP Sudarsana Kalluru
2017-01-29 15:35   ` Richard Cochran
2017-01-29 17:30     ` Mintz, Yuval
2017-01-29 21:02       ` Richard Cochran
2017-01-29 21:40         ` Mintz, Yuval
2017-01-30 14:34     ` David Laight
2017-01-30 17:55       ` Mintz, Yuval
2017-01-31 10:03         ` David Laight
2017-01-31 14:31           ` Mintz, Yuval
2017-01-31 14:53             ` Richard Cochran
2017-01-31 15:08               ` Mintz, Yuval
2017-01-31 17:43                 ` Richard Cochran [this message]
2017-01-29 15:09 ` [PATCH net-next v2 0/2] qed*: Add " Richard Cochran
2017-01-29 17:23   ` Mintz, Yuval

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=20170131174327.GA21731@localhost.localdomain \
    --to=richardcochran@gmail.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=Sudarsana.Kalluru@cavium.com \
    --cc=Yuval.Mintz@cavium.com \
    --cc=davem@davemloft.net \
    --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.