On Tue, Mar 17, 2015 at 05:21:47PM +0000, Chandra Mallela wrote: > ***Ours is typical telecom-networking profile. Could you point me to any info > link that defines the parameters for different profiles?
First of all, the telecom profile is unicast only. We do not support unicast. Secondly, from the telecom profile: A.3.4 REQUEST_UNICAST_TRANSMISSION TLV For requesting unicast Sync messages: The configurable range shall be one message every 16 seconds to 128 messages per second. No default rate is specified. For requesting unicast Delay_Resp messages: The configurable range shall be one message every 16 seconds to 128 messages per second. No default rate is specified. ITU-T G.8265.1 page 20 So, your 512 figure is *way* out of spec. > ***I understand the 1-step part. However, reducing DelayReq might not make > sense. Average path delay should be at least half the rate of Sync packets to > statistically arrive at better values of path delay. 1Hz seems quite low > especially for telecom applications. If the path is not changing, then it does not make sense to measure it so often. I would expect a telecom network to be engineered to have fixed delays. > I will google about SO_SELECT_ERR_QUEUE. However, if you have any good link, > please let me know. This means using Linux kernel version 3.10 or newer. Thanks, Richard ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Linuxptp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-users
