new errno ?

Hello, In working on the 802.11 refresh, I ran into a new errno code from FreeBSD: #define EDOOFUS 88 /* Programming error */ Shall we add this one? (Most likely with a different number since 88 is taken in the NetBSD errno.h.) I could use EPROTO instead, but

Re: new errno ?

In article <201807061021.35171.p...@netbsd.org>, Phil Nelson wrote: >Hello, > >In working on the 802.11 refresh, I ran into a new errno code from FreeBSD: > >#define EDOOFUS 88 /* Programming error */ > >Shall we add this one? (Most likely with a different number

Re: 8.0 performance issue when running build.sh?

Le 06/07/2018 à 16:48, Martin Husemann a écrit : On Fri, Jul 06, 2018 at 04:40:48PM +0200, Maxime Villard wrote: This are all successfull builds of HEAD for alpha that happened after June 1: What does that mean, are you building something *on* an Alpha CPU, or are you building the Alpha port

8.0 performance issue when running build.sh?

I have no scientific data yet, but just noticed that build times on the auto build cluster did rise very dramatically since it has been updated to run NetBSD 8.0 RC2. Since builds move around build slaves sometimes (not exactly randomly, but anyway) I picked the alpha port as an example (the

Re: new errno ?

On Friday 06 July 2018 12:09:55 Greg Troxel wrote: >  I might just map it to EFAULT or EINVAL. I like this suggestion. EFAULT --Phil

Re: interesting skylake perf tidbit

Le 18/06/2018 à 14:29, m...@netbsd.org a écrit : joerg called it stupid and said we should use monitor, he's probably right. new arm also has a similar thing. The thing is, there are several SPINLOCK_BACKOFF()s that we just can't replace by monitor. For example because we want to measure the

Re: mutex question

> On Jul 6, 2018, at 4:48 PM, Phil Nelson wrote: > > Hello, > >The FreeBSD 802.11 code is using a call to mtx_sleep(). The define is: > > #define mtx_sleep(chan, mtx, pri, wmesg, timo) \ >_sleep((chan), &(mtx)->lock_object, (pri), (wmesg), \

mutex question

Hello, The FreeBSD 802.11 code is using a call to mtx_sleep(). The define is: #define mtx_sleep(chan, mtx, pri, wmesg, timo) \ _sleep((chan), &(mtx)->lock_object, (pri), (wmesg), \ tick_sbt * (timo), 0, C_HARDCLOCK) Just in case I

Re: new errno ?

Phil Nelson writes: > Hello, > > In working on the 802.11 refresh, I ran into a new errno code from > FreeBSD: > > #define EDOOFUS 88 /* Programming error */ > > Shall we add this one? (Most likely with a different number since 88 is > taken > in the NetBSD

Re: new errno ?

On Fri, 6 Jul 2018 at 12:29, Phil Nelson wrote: > > On Friday 06 July 2018 12:09:55 Greg Troxel wrote: > > I might just map it to EFAULT or EINVAL. > > I like this suggestion. EFAULT For those interested in some of the history: