wireguard-openbsd/sys/arch/hppa/dev/pdc.c, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/hppa/dev/pdc.c?h=jd%2Fqueueboosts2018-02-19T08:59:52ZRemove almost unused `flags' argument of suser().2018-02-19T08:59:52Zmpimpi@openbsd.org2018-02-19T08:59:52Zurn:sha1:3e6763994aeb80a553b07ba51b1db2c4725c5c88
The account flag `ASU' will no longer be set but that makes suser()
mpsafe since it no longer mess with a per-process field.
No objection from millert@, ok tedu@, bluhm@
Compile in serial console settings support if any com(4) device is included2011-08-16T17:26:04Zketteniskettenis@openbsd.org2011-08-16T17:26:04Zurn:sha1:79bee3f9d53846a11da573700e7e5509dd39b1ad
in the kernel, not only when com @ gsc is there.
ok miod@
Move common code for waking up writers on a tty into a function.2010-07-02T17:27:01Znicmnicm@openbsd.org2010-07-02T17:27:01Zurn:sha1:4cc8800e3a0bcd323fb689c6f886d94920b8a5a8
ok deraadt matthew millert
Allow tty drivers to request larger buffers at attach time using a2010-06-28T14:13:25Zderaadtderaadt@openbsd.org2010-06-28T14:13:25Zurn:sha1:197ff252a2d579f1ae582e0b28a0b2a56ec2bb2f
max-baud-rate hint. Adjust TTYHOG (the nearly full logic) to this new
situation. The larger buffers are required by the very high speed
KDDI devices in Japan (CF com, or USB ucom) so those are the only two
drivers which currently ask for a larger buffer size.
ok yasuoka miod
cleanup more confusion regarding user.h before proc.h, or missing proc.h2010-04-20T23:26:59Zderaadtderaadt@openbsd.org2010-04-20T23:26:59Zurn:sha1:3b7eaf03a7fd51ac783cf4588c1ec14b128110c3
ok tedu
Some of the line disciplines want to check for suser. Better to pass them2010-04-12T12:57:51Ztedutedu@openbsd.org2010-04-12T12:57:51Zurn:sha1:79f6c33a904170343535140691e2309d78acab37
a process instead of using curproc. ok deraadt
Every selwakeup() should have a matching KNOTE() (even if kqueue isn't2009-11-09T17:53:38Znicmnicm@openbsd.org2009-11-09T17:53:38Zurn:sha1:270ebf02128560a47b9b980515d58ee07855c8d6
supported it doesn't do any harm), so put the KNOTE() in selwakeup() itself and
remove it from any occurences where both are used, except one for kqueue itself
and one in sys_pipe.c (where the selwakeup is under a PIPE_SEL flag).
Based on a diff from tedu.
ok deraadt
Use suser when possible. Suggested by miod@.2009-10-31T12:00:05Zfgschfgsch@openbsd.org2009-10-31T12:00:05Zurn:sha1:45f8a07e7f5e0632cea6b8574382a2991bc2f1cc
miod@ deraadt@ ok.
Add missing KNOTE() calls after selwakeup(), until we decide if the KNOTE()2009-10-31T06:40:14Zderaadtderaadt@openbsd.org2009-10-31T06:40:14Zurn:sha1:ade004edddcdab33faee7c7b5833d2bf917e71c0
calls can go directly into selwakeup() safely
long discussion with nicm, murmers of consent from tedu and miod, noone
else seems to care of kqueue is busted as long as it makes their sockets
move data fast... pretty sad.
Cleanup cn_pri. Change constants to more meaningful names, rather than2008-01-23T16:37:55Zjsingjsing@openbsd.org2008-01-23T16:37:55Zurn:sha1:713cf26678d1daf1bfade2209928a859d0bad373
the hp300 related ones currently in use. CN_NORMAL becomes CN_LOWPRI,
CN_INTERNAL becomes CN_MIDPRI and CN_REMOTE becomes CN_HIGHPRI.
ok miod@