netdev - Re: PTP_PEROUT_REQUEST and clock stepping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140912063310.GA6198@netboy>
Date:	Fri, 12 Sep 2014 08:33:10 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	Christian Riesch <christian.riesch@...cron.at>
Cc:	Daniel Glöckner <dg@...ix.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: PTP_PEROUT_REQUEST and clock stepping

On Fri, Sep 12, 2014 at 08:24:49AM +0200, Christian Riesch wrote:
> On Thu, Sep 11, 2014 at 11:52 AM, Daniel Glöckner <dg@...ix.com> wrote:
> > Only a small fraction of people
> > using periodic outputs will want to schedule the start of the signal at
> > a specific time in the future and only a fraction of those will use a
> > .period value that is so small that they can't use a timer to configure
> > the periodic output within .period/2 before the desired start time.
> 
> Ok, I got it now. So you are suggesting to change the behavior of
> PTP_PEROUT_REQUEST, aren't you? And break existing applications?
> Christian

I think he wants the periodic output to continue at the same phase and
frequency, even when you reset the clock time.

However, this is impossible to acheive because the hardware does not
support it.

Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html