Hi Richard,

Looks like the patch works fine. With this patch irrespective of port state
if BMCA selects new master it will trigger unicast state change, well port
state change will still trigger unicast state change.

But we have new request to make, for you to get a rough idea we have fpga in
between ptp4l and incoming packets.
Because ptp4l can dynamically change the master without cancelling the
services(sync and delay_resp) from previous master, the previous master
messages like sync and followup is causing unnecessary traffic at CPU and
fpga. We are using high packet rate for sync with two step enable.
Eventually this will timeout but if the timeout value is high then this will
be an issue.

It would be good if the ptp4l can support service(sync and delay) cancelling
and service(sync and delay) request when switching between the masters.

Thanks,
Pavan Lakote

> -----Original Message-----
> From: pavan-lakote [mailto:pavan-lak...@looptelecom.com]
> Sent: Monday, December 07, 2020 9:36 AM
> To: 'Richard Cochran'
> Cc: 'linuxptp-users@lists.sourceforge.net'
> Subject: RE: [Linuxptp-users] switchover fails when having multiple
unicast
> master
> 
> Okay, Let me try this. Thanks.
> 
> > -----Original Message-----
> > From: Richard Cochran [mailto:richardcoch...@gmail.com]
> > Sent: Sunday, December 06, 2020 12:28 PM
> > To: pavan-lakote
> > Cc: linuxptp-users@lists.sourceforge.net
> > Subject: Re: [Linuxptp-users] switchover fails when having multiple
> > unicast master
> >
> > On Fri, Nov 27, 2020 at 06:30:22AM -0800, Richard Cochran wrote:
> > > On Fri, Nov 13, 2020 at 10:27:56AM +0800, pavan-lakote wrote:
> > > > Can you please give me an rough idea when to expect a patch?
> > >
> > > Try this.
> >
> > Ping?
> >
> > Can you please try this patch and see if it fixes the issue?
> >
> > If it does, then I'll apply the patch to the code base.
> >
> > Thanks,
> > Richard
> >
> >
> > > ---8<---
> > > diff --git a/port.c b/port.c
> > > index fa49663..db3e9ac 100644
> > > --- a/port.c
> > > +++ b/port.c
> > > @@ -3209,6 +3209,9 @@ int port_state_update(struct port *p, enum
> > fsm_event event, int mdiff)
> > >           next = p->state_machine(next, event, 0);
> > >   }
> > >
> > > + if (mdiff) {
> > > +         unicast_client_state_changed(p);
> > > + }
> > >   if (next != p->state) {
> > >           port_show_transition(p, next, event);
> > >           p->state = next;
> > >




        
Loop Telecommunication International
        

        

Loop-V4150
DS0 Cross Connect Multiplexer supports up to 504E1/672T1 worth of DS0
non-blocking cross connect matrix. The V4150 DS0 Cross Connect System can
provide users with the high-density capacity up to 504 E1/T1, 24 T3MX3, or 8
STM-1 (OC-3). All interfaces are fully compliant for use with the relevant ETSI
standards and ITU recommendations. In addition, Loop-V4150 with E1/T1 cards,
through the protection relay shelf, is able to perform 1+1, 1:N and 1:1
redundancy switching to ensure the high-availability circuit system.
        


For further arrangement and more information, please contact Loop Telecom.
        



_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to