Re: [Linuxptp-users] Fw: “Resource temporarily unavailable” errors during flood ping test

[Mario M. <mar...@em...>]

Yes the increase tx_timestamp_retries is the correct way. Thanks for the hint.
My observation is that a increase on 3 of  this variable seems to help.
In the most retries case it seems to work with one retry. (my test platform MPC5200/DP83640)
With moderate stress test it seems no retries necessary. 

Thanks,
Mario
>
> On Tue, Oct 30, 2012 at 11:02:21PM +0000, Keller, Jacob E wrote:
> > 
> > It would take an insane amount of work to move to a model that
> > allows receive handling inside sk.c, and I believe it isn't worth
> > the effort. I would however like to increase the default
> > tx_timestamp_retries value, as 2 tries rarely works for anything
> > I've tested, as it generates false positive errors a lot.
> 
> Okay, what value is a safe default, in your experience?
> 
> > What hardware are you using that doesn't have issues at 2 retries?
> 
> The PHYTER almost never loses a Tx time stamp, and the TI CPTS seems
> to be working perfectly, too. I don't have the Freescale eTSEC (gianfar)
> for testing, but I remember that it always worked, since the Tx time
> stamp is delivered into packet buffer's padding.
> 
> With the IGB, sometimes it seemed that 2 retries is okay, but
> sometimes I needed to ramp this up.
> 
> > And have you attempted testing this under moderate stress?
> 
> I just retested the PHYTER under a ping flood, and there were no
> hiccups. I will test the CPTS again when I get a chance.
> 
> Thanks,
> Richard
>