typo in regress/sbin/newfs/checknewfs

2021-07-23 Thread alf
Hello, there seems to be a typo in regress/sbin/newfs/checknewfs, Alf Index: regress/sbin/newfs/checknewfs === RCS file: /cvs/src/regress/sbin/newfs/checknewfs,v retrieving revision 1.8 diff -u -p -r1.8 checknewfs ---

riscv64: slightly optimized copyin/copyout/kcopy

2021-07-23 Thread Jeremie Courreges-Anglas
I've been using a variation of this diff on my hifive unmatched since a few days. The goal is to at least optimize the aligned cases by using 8 or 4 bytes loads/stores. On this hifive unmatched, I found that unaligned 8 or 4 bytes loads/stores loops are utterly slow, much slower than

Re: riscv64: slightly optimized copyin/copyout/kcopy

2021-07-23 Thread Mark Kettenis
> From: Jeremie Courreges-Anglas > Date: Fri, 23 Jul 2021 11:54:51 +0200 > Content-Type: text/plain > > > I've been using a variation of this diff on my hifive unmatched since > a few days. The goal is to at least optimize the aligned cases by using > 8 or 4 bytes loads/stores. On this hifive

Re: riscv64: slightly optimized copyin/copyout/kcopy

2021-07-23 Thread Jeremie Courreges-Anglas
On Fri, Jul 23 2021, Mark Kettenis wrote: >> From: Jeremie Courreges-Anglas >> Date: Fri, 23 Jul 2021 11:54:51 +0200 >> Content-Type: text/plain >> >> >> I've been using a variation of this diff on my hifive unmatched since >> a few days. The goal is to at least optimize the aligned cases by

iwm(4): enable on riscv64

2021-07-23 Thread Ashton Fagg
The following diffs adds iwm(4) to the riscv64 kernel config. I tested this with the following device: iwm0 at pci5 dev 0 function 0 "Intel Dual Band Wireless-AC 9260" rev 0x29, intx icarus$ ifconfig iwm0 iwm0: flags=808843 mtu 1500 lladdr bc:54:2f:cb:3b:21 index 2 priority 4

Re: forwarding in parallel ipsec workaround

2021-07-23 Thread Hrvoje Popovski
On 23.7.2021. 16:20, Vitaliy Makkoveev wrote: > On Thu, Jul 22, 2021 at 11:30:02PM +0200, Hrvoje Popovski wrote: >> On 22.7.2021. 22:52, Vitaliy Makkoveev wrote: >>> On Thu, Jul 22, 2021 at 08:38:04PM +0200, Hrvoje Popovski wrote: On 22.7.2021. 12:21, Hrvoje Popovski wrote: > Thank you

unwind(8): don't doubt secure answers on network change

2021-07-23 Thread Florian Obser
Do not doubt a secure (i.e. validated) NXDOMAIN response when we just switched networks. We just validated it! While here reorder the long list of conditions to make it easier to understand when we doubt a response because we might be behind a captive portal. First list all conditions when we do

unwind(8): store enabled resolvers lookup table in config

2021-07-23 Thread Florian Obser
We store a list of resolver strategies in order of their preference in the configuration struct. This is also an implicit list of enabled resolver strategies. We have also stored an explict lookup array of enabled strategies outside of the configuration to be able to quickly answer "is this

Re: forwarding in parallel ipsec workaround

2021-07-23 Thread Vitaliy Makkoveev
On Thu, Jul 22, 2021 at 11:30:02PM +0200, Hrvoje Popovski wrote: > On 22.7.2021. 22:52, Vitaliy Makkoveev wrote: > > On Thu, Jul 22, 2021 at 08:38:04PM +0200, Hrvoje Popovski wrote: > >> On 22.7.2021. 12:21, Hrvoje Popovski wrote: > >>> Thank you for explanation.. > >>> > >>> after hitting box all

rpki-client: adjust HTTP/1.1 request string

2021-07-23 Thread Job Snijders
Hi all, Based on suggestions from Julian Reschke. * "Connection: keep-alive" isn't needed, as the HTTP 1.1 default is to use persistent connections (RFC 7230, section 6.3). * "Host" is recommended to be in the front. * "Accept-Encoding: identity" makes it clear to the server compression

Re: rpki-client: adjust HTTP/1.1 request string

2021-07-23 Thread Sebastian Benoit
Job Snijders(j...@openbsd.org) on 2021.07.23 15:23:49 +: > Hi all, > > Based on suggestions from Julian Reschke. > > * "Connection: keep-alive" isn't needed, as the HTTP 1.1 default is to > use persistent connections (RFC 7230, section 6.3). > > * "Host" is recommended to be in the front.

snmpd(8): Allow setting engineid

2021-07-23 Thread Martijn van Duren
This diff introduces setting the engineid for snmpd(8). Although this diff might seem quite excessive at first glance, there's a valid reason to do so. The following things are in effect when sending an SNMPv3 trap: - SNMP trap packets are unacknowledged; meaning that we don't get a response -,

Re: riscv64: slightly optimized copyin/copyout/kcopy

2021-07-23 Thread Mark Kettenis
> From: Jeremie Courreges-Anglas > Date: Fri, 23 Jul 2021 13:54:31 +0200 > > On Fri, Jul 23 2021, Mark Kettenis wrote: > >> From: Jeremie Courreges-Anglas > >> Date: Fri, 23 Jul 2021 11:54:51 +0200 > >> Content-Type: text/plain > >> > >> > >> I've been using a variation of this diff on my

Re: rpki-client: adjust HTTP/1.1 request string

2021-07-23 Thread Claudio Jeker
On Fri, Jul 23, 2021 at 05:28:33PM +0200, Sebastian Benoit wrote: > Job Snijders(j...@openbsd.org) on 2021.07.23 15:23:49 +: > > Hi all, > > > > Based on suggestions from Julian Reschke. > > > > * "Connection: keep-alive" isn't needed, as the HTTP 1.1 default is to > > use persistent

less(1): refreshing file of size 0 results in file being treated as a pipe

2021-07-23 Thread user
Less contains a hack to force files of size 0 to become non-seekable in order to workaround a linux kernel bug. When the file becomes non-seekable any further reads from the file are appended rather than overwriting the original contents of the file. diff --git ch.c ch.c index