On Tue, Jul 04, 2017 at 01:24:58PM +0200, Richard Cochran wrote: > On Tue, Jul 04, 2017 at 06:32:19PM +0800, Hangbin Liu wrote: > > On Tue, Jul 04, 2017 at 11:02:26AM +0200, Richard Cochran wrote: > > > > Back to this question, do you still want to move rtnl socket from clock > > > > to > > > > per port? > > > > > > Yes, but only if we can use a single rtnl socket for both messages. > > I meant to say, a single rtnl socket per-port.
Cool. Sorry for the misunderstanding. > > > So I think we need to make each port have their own rtnl socket fd. Then > > each > > fd get their own multicast rtnl message. > > > > What do you think? > > Yes, that is what I meant. > > My question was, can we have both RTNLGRP_LINK and ifinfomsg on the > same per-port socket? (I assume that works.) Yes, it works. Thanks Hangbin ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
