wireguard-openbsd/sys, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys?h=jd%2Fqueueboosts2020-06-23T04:31:03ZMark interface as MPSAFE2020-06-23T04:31:03ZJason A. DonenfeldJason@zx2c4.com2020-06-23T04:21:54Zurn:sha1:fb099766628c04eb037969aacdcb0ff94b4cfe4f
This enables us to process queueing of different packet queues in
without NET_LOCK. Combined with the increase in txlen, this keeps our
encryption workers more active. This results in a ~30% performance
boost.
Increase if_txmit to 642020-06-23T04:24:09ZJason A. DonenfeldJason@zx2c4.com2020-06-23T04:18:04Zurn:sha1:1807dd1a1529b4426d7d3c99a4709bbf7598d19e
This increases throughput by keeping the worker threads active for
longer.
add intrmap_one, some temp code to help us write pci_intr_establish_cpu.2020-06-23T01:40:03Zdlgdlg@openbsd.org2020-06-23T01:40:03Zurn:sha1:f90eedca1997d2d936d5eda120168facc50b725b
it means we can do quick hacks to existing drivers to test interrupts
on multiple cpus. emphasis on quick and hacks.
ok jmatthew@, who will also ok the removal of it at the right time.
Implement pci_intr_establish_cpu() for pyro(4) and vpci(4) based sparc642020-06-23T01:21:29Zjmatthewjmatthew@openbsd.org2020-06-23T01:21:29Zurn:sha1:1d9e937e45405d8fccbf06a258cd97fbc51591ce
systems. MSIs on these systems are delivered to event queues, which
trigger interrupts when non-empty. The interrupt handler dequeues the
MSIs and converts them into soft interrupts, which run on the same cpu
as the event queue interrupt.
To target pci device interrupts to different cpus, we set up an event
queue per cpu in the system, or as many as we can, if there are fewer
event queues available. For now, we don't have a way to feed this
information back to intrmap, so instead we just map interrupts for cpus
that don't have an event queue to another cpu that does have one.
Tested on V215 (pyro), T5120, T4-1, S7-2 (vpci).
dlg@ got the pyro side of it working for me.
ok dlg@ kettenis@
timecounting: add gettime(9), getuptime(9)2020-06-22T21:16:07Zchelohacheloha@openbsd.org2020-06-22T21:16:07Zurn:sha1:8dca5d44636110d0ff0cfe71785c8f18da7ca99e
time_second and time_uptime are used widely in the tree. This is a
problem on 32-bit platforms because time_t is 64-bit, so there is a
potential split-read whenever they are used at or below IPL_CLOCK.
Here are two replacement interfaces: gettime(9) and getuptime(9).
The "get" prefix signifies that they do not read the hardware
timecounter, i.e. they are fast and low-res. The lack of a unit
(e.g. micro, nano) signifies that they yield a plain time_t.
As an optimization on LP64 platforms we can just return time_second or
time_uptime, as a single read is atomic. On 32-bit platforms we need
to do the lockless read loop and get the values from the timecounter.
In a subsequent diff these will be substituted for time_second and
time_uptime almost everywhere in the kernel.
With input from visa@ and dlg@.
ok kettenis@
Add opalcons(4), a driver for the OPAL console.2020-06-22T21:13:40Zketteniskettenis@openbsd.org2020-06-22T21:13:40Zurn:sha1:9cff15ef82ea860b6c29be0e577000460a15a956The minimum frame size for the ELFv2 ABI is 32 bytes. Using this value2020-06-22T18:49:36Zketteniskettenis@openbsd.org2020-06-22T18:49:36Zurn:sha1:4d943fd61ab7ebc3390510da6f072b3fbd6ff841
instead of 48 in the trap setup functions makes it possible to get rid
of the magic offset in proc_trampoline.
Suggested by gkoehler@
inittodr(9): introduce dedicated flag to enable writes from resettodr(9)2020-06-22T18:25:57Zchelohacheloha@openbsd.org2020-06-22T18:25:57Zurn:sha1:bf2d84a07eb2512358d130f21cd3f3c03b4c2d28
We don't want resettodr(9) to write the RTC until inittodr(9) has
actually run. Until inittodr(9) calls tc_setclock() the system UTC
clock will contain a meaningless value and there's no sense in
overwriting a good value with a value we know is nonsense.
This is not an uncommon problem if you're debugging a problem in early
boot, e.g. a panic that occurs prior to inittodr(9).
Currently we use the following logic in resettodr(9) to inhibit writes:
if (time_second == 1)
return;
... this is too magical.
A better way to accomplish the same thing is to introduce a dedicated
flag set from inittodr(9). Hence, "inittodr_done".
Suggested by visa@.
ok kettenis@
Enable interrupts when they were enabled before the trap (except when we2020-06-22T18:15:50Zketteniskettenis@openbsd.org2020-06-22T18:15:50Zurn:sha1:be00ebe64ffda37c7ac803f330b1c897f12b55ea
are handling "genuine" interrupts like the decrementer and hypervisor
virtualization interrupts).
Handle data storage and data segment interrupts from userland as well.2020-06-22T18:03:22Zketteniskettenis@openbsd.org2020-06-22T18:03:22Zurn:sha1:c0e8dfc26859acc5c80a7cd731a9232aad396d94