On Tue, Dec 10, 2013 at 08:53:27PM +0000, Keller, Jacob E wrote:
> 
> I'm not too familiar with management.. is it possible for management
> messages to come in via the network socket?

Yes, but I think this special push information should only appear on
the loacl UDS interface. Putting unsolicited messages on the network
would go against the standard.

The idea is to make life easier for local programs like phc2sys.
 
> Create an array of things which can be pushed, then if the array
> slot is not null, it's a linked list of all the requests so far?
> (assuming correct that we want to support multiple clients
> requesting) Then each request could be a store of the address that
> requested that push notification? Linked list in this case would be
> fairly cheap, and we wouldn't have to sort them. The hash enables
> fast lookup of each push notification without having to scan a
> single list for every push notification.

First of all, we will not have that many local listeners, maybe just
phc2sys and perhaps one or two others. So, we don't need to get too
fancy.

In uds.c, we can keep a list of {address, msg_bitmap} where the bit
map has slots for the different management messages like "current data
set", "parent data set", and so on.

We will have to add hooks throughout the code that trigger when the
program state changes in such a way as to change one of the possible
data sets represented by msg_bitmap. The hook will simply send the
needed message or messages.

Then, the code uds.c will match the message type against each list
entry and send it if it matches.

Thanks,
Richard


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to