Dear all,
I like to run rpki-client very often, and not be bogged down with
non-responsive respositories. If a repository is uncommunicative,
rpki-client as-is will try other transports, or come back later (because
of a next crontab invocation).
In rpki-client, RSYNC & HTTPS timeouts now are unif
There have to be some strict-aligned architectures which don't emulate
unaligned access, because there will always be architectures which have
a high emulation cost, and I'm ok with alpha joining that group.
Miod Vallat wrote:
> The alpha part contains code in the kernel to handle unaligned mem
On Tue, 09 Aug 2022 19:39:31 -, Miod Vallat wrote:
> The alpha part contains code in the kernel to handle unaligned memory
> accesses from userland programs, to prevent them from dying in horrible
> SIGBUS.
>
> This made sense in the '90s, but since then people have learned to work
> with stri
On Tue, Aug 09, 2022 at 07:39:31PM +, Miod Vallat wrote:
> The alpha part contains code in the kernel to handle unaligned memory
> accesses from userland programs, to prevent them from dying in horrible
> SIGBUS.
>
> This made sense in the '90s, but since then people have learned to work
> wit
On Tue, Aug 09, 2022 at 06:02:10PM +, Miod Vallat wrote:
> > Other platforms (architectures?) (powerpc, powerpc64, arm64, riscv64)
> > multiplex their singular interrupt clock to schedule both a
> > fixed-period hardclock and a pseudorandom statclock.
> >
> > This is the direction I intend to
Hi,
httpd's autogenerated pages (file index and error page) should use the
"viewport" meta tag, because they would be better displayed on mobile
devices in my opinion.
--
matthias
diff --git usr.sbin/httpd/server_file.c usr.sbin/httpd/server_file.c
index 786f3677422..a09a5264e62 100644
--- usr
The alpha part contains code in the kernel to handle unaligned memory
accesses from userland programs, to prevent them from dying in horrible
SIGBUS.
This made sense in the '90s, but since then people have learned to work
with strict-alignment architectures, and this code has been less and
less tr
The revert of zlib.h r1.7 led to one or two compiler warnings in
ctfdump, depending on the architecture:
/usr/src/usr.bin/ctfdump/ctfdump.c:704:7: warning: format specifies type
'unsigned long long' but the argument has type 'uLong' (aka 'unsigned long')
[-Wformat]
stream.tot
> Other platforms (architectures?) (powerpc, powerpc64, arm64, riscv64)
> multiplex their singular interrupt clock to schedule both a
> fixed-period hardclock and a pseudorandom statclock.
>
> This is the direction I intend to take every platform, mips64
> included, after the next release.
>
> In
On Tue, Aug 09, 2022 at 06:58:05PM +0200, Hrvoje Popovski wrote:
> Hi all,
>
> I've sysupgrade firewall from
> OpenBSD 7.2-beta (GENERIC.MP) #651: Tue Jul 26 23:11:26 MDT 2022
> to
> OpenBSD 7.2-beta (GENERIC.MP) #677: Mon Aug 8 18:58:49 MDT 2022
>
> and on console there was lot's of spalassert
Hi all,
I've sysupgrade firewall from
OpenBSD 7.2-beta (GENERIC.MP) #651: Tue Jul 26 23:11:26 MDT 2022
to
OpenBSD 7.2-beta (GENERIC.MP) #677: Mon Aug 8 18:58:49 MDT 2022
and on console there was lot's of spalassert like below. I'm having ix,
aggr and vlan on that firewall
splassert: vlan_ioctl
On Tue, Aug 09, 2022 at 02:56:54PM +, Miod Vallat wrote:
> > Do those machines not have Coprocessor 0? If they do, why would you
> > prefer glxclk over CP0?
>
> cop0 only provides one timer, from which both the scheduling clock and
> statclk are derived. glxclk allows two timers to be used, a
> Do those machines not have Coprocessor 0? If they do, why would you
> prefer glxclk over CP0?
cop0 only provides one timer, from which both the scheduling clock and
statclk are derived. glxclk allows two timers to be used, and thus can
provide a more reliable statclk (see the Torek paper, etc -
On Tue, Aug 09, 2022 at 02:03:31PM +, Visa Hankala wrote:
> On Mon, Aug 08, 2022 at 02:52:37AM -0500, Scott Cheloha wrote:
> > One thing I'm still uncertain about is how glxclk fits into the
> > loongson picture. It's an interrupt clock that runs hardclock() and
> > statclock(), but the code d
On Mon, Aug 08, 2022 at 02:52:37AM -0500, Scott Cheloha wrote:
> One thing I'm still uncertain about is how glxclk fits into the
> loongson picture. It's an interrupt clock that runs hardclock() and
> statclock(), but the code doesn't do any logical masking, so I don't
> know whether or not I need
On Tue, Aug 09, 2022 at 08:42:37AM +, Klemens Nanni wrote:
> All of them are passed to inspect/copy out fields, none of the functions
> writes to the struct.
>
> This makes it easier to argue about code (in MP context).
>
> For this to work, ifa_ifwithaddr(), ifa_ifwithdstaddr() and
> ifaof_i
All of them are passed to inspect/copy out fields, none of the functions
writes to the struct.
This makes it easier to argue about code (in MP context).
For this to work, ifa_ifwithaddr(), ifa_ifwithdstaddr() and
ifaof_ifpforaddr() need const arguments as well (matching the behaviour).
Expand th
17 matches
Mail list logo
