I agree with ratchov that in this instance, precise timing isn't important.
10 Dec 2022 05:53:48 Alexandre Ratchov :
> On Fri, Dec 09, 2022 at 12:43:31PM -0600, Scott Cheloha wrote:
>> On Fri, Dec 09, 2022 at 12:10:59PM +0100, Alexandre Ratchov wrote:
>>> This diff adds an option to display
On Sat, Dec 10, 2022 at 11:32:08PM +0300, Vitaliy Makkoveev wrote:
> The netlock removal within nd6_dad_timer() is wrong. It protects
> `ifa’, `ia6’ and ip6 output path.
Yes... Sorry for noise, I'll come back with a less stupid diff.
On Fri, Dec 09 2022, Scott Cheloha wrote:
> Next up for the armv7 clockintr switch: amptimer(4).
>
> - Remove amptimer-specific clock interrupt scheduling bits and
> randomized statclock bits.
> - Remove debug evcounts. The interrupt's evcount counts all clock
> interrupts from now on.
> -
The netlock removal within nd6_dad_timer() is wrong. It protects
`ifa’, `ia6’ and ip6 output path.
> On 10 Dec 2022, at 15:16, Klemens Nanni wrote:
>
> nd6_nbr.c's static list of IPs to perform Duplicate Address Detection on
> is protected by the too broad exclusive net lock.
>
> Switch
It's not required because `dp' was just allocated with M_ZERO flag.
Index: sys/netinet6/nd6_nbr.c
===
RCS file: /cvs/src/sys/netinet6/nd6_nbr.c,v
retrieving revision 1.138
diff -u -p -r1.138 nd6_nbr.c
--- sys/netinet6/nd6_nbr.c
Scott Cheloha:
> The UltraSPARC IIe's %TICK register has a variable frequency.
> miod@ confirmed that the problem is real.
Indeed, I remember clocking down the Blade 100 with apm(8).
Somebody with access to the hardware might want to adapt the NetBSD
code that adds timecounter support for the
Updated patch looks good to me.
- todd
On Sat, Dec 10, 2022 at 10:24:52AM -0700, Theo de Raadt wrote:
> Scott Cheloha wrote:
>
> > On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> > > Mark Kettenis wrote:
> > >
> > > > So really the question is whether we should register the "tick"
> > > > timecounter if we also
Mark Kettenis wrote:
> So really the question is whether we should register the "tick"
> timecounter if we also provide the "stick" or "sys_tick" timecounter.
>
> Personaly I think the code we currently have is fine. If you make the
> sconscious decision to use "tick" on a system that provides
nd6_nbr.c's static list of IPs to perform Duplicate Address Detection on
is protected by the too broad exclusive net lock.
Switch nd6_dad_timer() and helpers to a dedicated dad_lk rwlock(9) to
take pressure of the net lock.
A mutex(9) must not be used as this code path may sleep:
On Sat, Dec 10, 2022 at 03:14:37PM +0100, Mark Kettenis wrote:
> > Date: Fri, 9 Dec 2022 16:27:59 -0600
> > From: Scott Cheloha
> >
> > The UltraSPARC IIe's %TICK register has a variable frequency. See
> > section 2.3 in this document here:
> >
> >
On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> Mark Kettenis wrote:
>
> > So really the question is whether we should register the "tick"
> > timecounter if we also provide the "stick" or "sys_tick" timecounter.
> >
> > Personaly I think the code we currently have is fine. If
Scott Cheloha wrote:
> On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> > Mark Kettenis wrote:
> >
> > > So really the question is whether we should register the "tick"
> > > timecounter if we also provide the "stick" or "sys_tick" timecounter.
> > >
> > > Personaly I think
> Date: Fri, 9 Dec 2022 16:27:59 -0600
> From: Scott Cheloha
>
> The UltraSPARC IIe's %TICK register has a variable frequency. See
> section 2.3 in this document here:
>
>
Sorry for the delay.
On Thu, Nov 10, 2022 at 08:19:51PM +0100, Ingo Schwarze wrote:
> Hi Scott,
>
> thanks for repeatedly working on time-related library documentation. :-)
>
> Unless noted otherwise, i agree with Todd's comments.
>
> Todd C. Miller wrote on Wed, Nov 09, 2022 at 10:31:15AM
As with e.g. kstat(1), implementing a periodic display with
nanosleep(2) causes the display interval to drift. Doing it with
setitimer(2) prevents drift.
ok?
Index: iostat.c
===
RCS file: /cvs/src/usr.sbin/iostat/iostat.c,v
On Sat, Dec 10, 2022 at 02:43:50PM +0100, Christian Weisgerber wrote:
> Scott Cheloha:
>
> > The UltraSPARC IIe's %TICK register has a variable frequency.
> > miod@ confirmed that the problem is real.
>
> Indeed, I remember clocking down the Blade 100 with apm(8).
>
> Somebody with access to
> Date: Sat, 10 Dec 2022 09:43:32 -0600
> From: Scott Cheloha
>
> On Sat, Dec 10, 2022 at 03:14:37PM +0100, Mark Kettenis wrote:
> > > Date: Fri, 9 Dec 2022 16:27:59 -0600
> > > From: Scott Cheloha
> > >
> > > The UltraSPARC IIe's %TICK register has a variable frequency. See
> > > section 2.3
Dead since introduction in 2001 with icmp6.c r1.31:
implement upper limit to icmp6 redirects (experimental, turned off)
negative value to {mtudisc,redirect}_{hi,lo}wat will turn off the
limitation.
sync with kame.
icmp6_redirect_lowat was always -1 and never hit the empty
tech@,
The below diff tweaks how vmd and vmm define memory ranges (adding a
"type" attribute) so we can properly build an e820 memory map to hand to
things like SeaBIOS or the OpenBSD ramdisk kernel (when direct booting
bsd.rd).
Why do it? We've been carrying a few patches to SeaBIOS in the
Hi Scott,
Scott Cheloha wrote on Sat, Dec 10, 2022 at 09:25:48AM -0600:
> Sure, I will keep the ERRORS section.
> I think the current phrasing in ERRORS is odd, though.
> "may set the global variable..." is what we normally say here, but it
> isn't a "may" in this case, it's an "always".
I
ok mvs@
> On 11 Dec 2022, at 01:46, Klemens Nanni wrote:
>
> Dead since introduction in 2001 with icmp6.c r1.31:
>implement upper limit to icmp6 redirects (experimental, turned off)
>negative value to {mtudisc,redirect}_{hi,lo}wat will turn off the
> limitation.
>sync with kame.
>
22 matches
Mail list logo
