wireguard-openbsd/sys/kern/sys_generic.c, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/kern/sys_generic.c?h=jd%2Fqueueboosts2020-03-20T04:11:05Zpoll(2), ppoll(2), pselect(2), select(2): tsleep(9) -> tsleep_nsec(9)2020-03-20T04:11:05Zchelohacheloha@openbsd.org2020-03-20T04:11:05Zurn:sha1:2e0a843148d4bb05177fa689bb58d713508abc8c
With input from visa@.
ok visa@
Push the KERNEL_LOCK() insidge pgsigio() and selwakeup().2020-02-14T14:32:44Zmpimpi@openbsd.org2020-02-14T14:32:44Zurn:sha1:112e0b7cd8c0810f5e6ec8c11d147cff217a606d
The 3 subsystems: signal, poll/select and kqueue can now be addressed
separatly.
Note that bpf(4) and audio(4) currently delay the wakeups to a separate
context in order to respect the KERNEL_LOCK() requirement. Sockets (UDP,
TCP) and pipes spin to grab the lock for the sames reasons.
ok anton@, visa@
Make writes to the f_flag field of `struct file' MP-safe using atomic2020-02-01T08:57:27Zantonanton@openbsd.org2020-02-01T08:57:27Zurn:sha1:1672369d9e9dbbbf8a2805c3bf77cdcdea101f66
operations. Since the type of f_flag must change in order to use the
atomic(9) API, reorder the struct in order to avoid padding; as pointed
out by tedu@.
ok mpi@ visa@
Introduce wakeup_proc() a function to un-SSTOP/SSLEEP a thread.2020-01-16T16:35:03Zmpimpi@openbsd.org2020-01-16T16:35:03Zurn:sha1:9566af8920ce0c73af22f6155f3428b247ad2cc0
This moves most of the SCHED_LOCK() related to protecting the sleepqueue
and its states to kern/kern_sync.c
Name suggestion from jsg@, ok kettenis@, visa@
Unify handling of ioctls FIOSETOWN/SIOCSPGRP/TIOCSPGRP and2020-01-08T16:27:40Zvisavisa@openbsd.org2020-01-08T16:27:40Zurn:sha1:36b1b8b4dfaf3411193c17c2462937014292f2df
FIOGETOWN/SIOCGPGRP/TIOCGPGRP. Do this by determining the meaning of
the ID parameter inside the sigio code. Also add cases for FIOSETOWN
and FIOGETOWN where there have been TIOCSPGRP and TIOCGPGRP before.
These changes allow removing the ID translation from sys_fcntl() and
sys_ioctl().
Idea from NetBSD
OK mpi@, claudio@
poll(2), ppoll(2), select(2), pselect(2): always set P_SELECT before tsleep2019-10-03T18:47:19Zchelohacheloha@openbsd.org2019-10-03T18:47:19Zurn:sha1:ade044871aeb7873c05f673982d81204f7bf8fe3
When I introduced the tsleep loops in r1.23 I screwed it up and introduced
a bug: on EWOULDBLOCK we loop but fail to reset P_SELECT, so the thread
will continue to sleep but miss all relevant descriptor activity after
INT_MAX ticks have elapsed.
Spotted by mpi@ back in July.
ok mpi@
push the KERNEL_LOCK deeper on read(2) and write(2)2019-06-22T06:48:25Zsemariesemarie@openbsd.org2019-06-22T06:48:25Zurn:sha1:86391f5b5115a6d519715ab2f01b810532dfbdab
unlocks read(2) and write(2) syscalls families, and push the KERNEL_LOCK
deeper in the code path. KERNEL_LOCK is managed per file type in fileops
handlers (fo_read, fo_write, and fo_close). read(2) and write(2) on
socket are KERNEL_LOCK-free.
initial work from mpi@ and ians@
ok mpi@ kettenis@ visa@ ians@
Make resource limit access MP-safe. So far, the copy-on-write sharing2019-06-21T09:39:48Zvisavisa@openbsd.org2019-06-21T09:39:48Zurn:sha1:edc99bcd885f4004d6cffdbe82f15aa2eb27ee9c
of resource limit structs has been done between processes. By applying
copy-on-write also between threads, threads can read rlimits in
a nearly lock-free manner.
Inspired by code in DragonFly BSD and FreeBSD.
OK mpi@, agreement from jmatthew@ and anton@
select(2), pselect(2), poll(2), ppoll(2): Support full timeout range.2019-01-21T23:41:26Zchelohacheloha@openbsd.org2019-01-21T23:41:26Zurn:sha1:82dc0b3f15d8667b425ec92394bac57c356052cb
Remove the arbitrary and undocumented 24hr limits for timeouts from these
interfaces. To do so, loop tsleep(9) to chip away at timeouts larger than
what tsleep(9) can handle in one call.
Use timerisvalid(3)/timespecisvalid() for input validation instead of
itimerfix()/timespecfix() to avoid the 100 million second upper bounds
those functions introduce.
POSIX requires support for timeouts of at least 31 days for select(2) and
pselect(2), so these changes make our implementation more compliant.
Other improvements here include better variable names for the time stuff
and more consolidated timeout logic with less backwards goto jumping, all
of which made dopselect() and doppoll() a bear to read.
Naming improvements prompted by tedu@ in a prior patch for nanosleep(2).
With input from deraadt@. Validation bug spotted by matthew@ in an earlier
version.
ok visa@
Reorder checks in the read/write(2) family of syscalls to prepare making2018-08-20T16:00:22Zmpimpi@openbsd.org2018-08-20T16:00:22Zurn:sha1:2bd648c0c791046970147cb6db731832ad511740
file operations mp-safe.
This change makes it clear that `f_offset' is only accessed in vn_read()
and vn_write(), which will help taking it out of the KERNEL_LOCK().
This refactoring uncovered a race in vn_read() which is now documented
and will be addressed in a later diff.
ok visa@