linux-kernel - Re: [PATCH] firewire: adopt read cycle timer ABI from raw1394

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: <4701E902.3070104@monom.org>
Date:	Tue, 02 Oct 2007 08:45:22 +0200
From:	Daniel Wagner <wagi@...om.org>
To:	Kristian Høgsberg <krh@...planet.net>
CC:	Pieter Palmers <pieterp@...w.be>,
	Kristian Høgsberg <krh@...hat.com>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firewire: adopt read cycle timer ABI from raw1394

>>> Pieter, do applications like yours need the cycle counter only for a few
>>> predetermined packets or for each and every packet?
>> We need it for every packet for two reasons:
>> 1) it's the only way to determine how many packets were dropped when
>> packet drops are flagged in the callback
> 
> Your application should know what the timestamp should be for each iso
> receive callback and if you see a larger value than expected you can
> use that to calculate how many cycles were lost.

That might not work if the device is synchronized to SPDIF for example. 
In this case it is possible (and very likely) that the two clock domains 
(SPDIF and the firewire bus) drift. The time difference between two 
timestamps do not have to be the same all the time. So it can be hard 
(possible?) to predict the next timestamp correctly.

daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/