Re: [Linuxptp-devel] [PATCH 0/3] Terminate timemaster when memory allocation fails

2015-08-29 Thread Richard Cochran
On Fri, Aug 28, 2015 at 05:06:29PM +0200, Miroslav Lichvar wrote: > As per the discussion on linuxptp-users, this is a set that tries to > fix the unhandled errors in memory allocation in timemaster. Series applied. Thanks, Richard

[Linuxptp-devel] [PATCH RFC v1 0/4] Hybrid "Enterprise" E2E Mode

2015-08-29 Thread Richard Cochran
This series add support for the so-called hybrid mode, letting the delay request/response messages be unicast while keeping the other messages multicast. The code works over all three transports, L2, UDPv4, and UDPv6, although I did not test UDPv6. This series requires two other recent patches:

[Linuxptp-devel] [PATCH RFC v1 4/4] Support hybrid E2E using unicast delay requests and responses.

2015-08-29 Thread Richard Cochran
The draft Enterprise Profile [1] specifies a hybrid E2E delay mechanism, where the delay response message is sent "in kind". That is, if the request is unicast, then the response is also unicast. Apparently this scheme is already in widespread use in some industries. Also, it makes sense, becaus

[Linuxptp-devel] [PATCH RFC v1 1/4] udp: set the destination port unconditionally.

2015-08-29 Thread Richard Cochran
Even if the caller provides the destination address, still the port must depend on the passed 'event' value for correct delivery. Signed-off-by: Richard Cochran --- udp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/udp.c b/udp.c index b8aa76a..48d18d8 100644 --- a/udp

[Linuxptp-devel] [PATCH RFC v1 2/4] udp6: set the destination port unconditionally.

2015-08-29 Thread Richard Cochran
Even if the caller provides the destination address, still the port must depend on the passed 'event' value for correct delivery. Signed-off-by: Richard Cochran --- udp6.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/udp6.c b/udp6.c index fdf5799..10ff166 100644 --- a

[Linuxptp-devel] [PATCH RFC v1 3/4] Use the standardized low level socket address format.

2015-08-29 Thread Richard Cochran
The raw Ethernet transport code invented its own way of storing the MAC address into our "struct address" data structure. However, this private format is incompatible with the sockaddr_ll returned from the networking stack. This patch converts the code to use the proper format. Signed-off-by: Ri