summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-12-26enable shrinker for ttmJonathan Gray
ok kettenis@
2019-12-26Add a number of new formats to inspect what sessions and clients aNicholas Marriott
window is present or active in. From Tyler Culp in GitHub issue 2034.
2019-12-26Add point-to-point support for broadcast interfaces.remi
tested by Kapetanakis Giannis ok denis@
2019-12-26It is believed that an implementation of madvise was available inJonathan Gray
SunOS 4.0 based on text from the following papers. "Two 4.2BSD system calls, madvise and mincore, remain unspecified, madvise is intended to provide information to the system to influence its management policies. Since a major rework of such policies was deferred to a future release, we decided to defer full specification and implementation of madvise until that time." R. Gingell, J. Moran, W. Shannon "Virtual Memory Architecture in SunOS" Proceedings of USENIX Summer Conference, June 1987 AUUGN Volume 8 Number 5, October 1987 "Memory management related system calls based on the original 4.2BSD specification that were implemented include mmap, munmap, mprotect, madvise, and mincore." J. Moran "SunOS Virtual Memory Implementation" Proceedings of the Spring 1988 European UNIX Users Group Conference, April 1988 AUUGN Volume 9 Number 3, June 1988 and a reference in "Global Index", Part Number: 800-1758-10, Revision A, of 9 May 1988 bitsavers pdf/sun/sunos/4.0/800-1758-10A_Global_Index_198805.pdf discussed with an ok schwarze@
2019-12-25exit_type is already set up with exactly the information we need,Marc Espie
so get rid of cluttered duplicate logic okay kn@
2019-12-25disable a few more things which might look in /usr/local.Theo de Raadt
(I decided to take a look at ktrace -di output of the whole compilation procedure)
2019-12-25Replace macros knote_alloc() and knote_free() with direct use ofVisa Hankala
pool_get() and pool_put(). This makes it clearer that the knote allocation cannot fail and that the error check is unnecessary. OK anton@, kettenis@, mpi@
2019-12-25Use FOREACH macro to iterate over mnt_vnodelist.Alexander Bluhm
OK millert@ visa@ benno@
2019-12-25WSDISPLAYIO_GTYPE is u_int not intJonathan Gray
2019-12-25Hook up the shrinker for inteldrm(4). This is a "light" version that onlyMark Kettenis
drops graphics buffers that are cached and not in active use. Help from beck@ for pointing out how to hook this up to our pagedaemon. ok jsg@
2019-12-25Condense a few multi line comments into single line ones. While hereanton
turn them into proper sentences. Gets rid of 27 lines in total.
2019-12-25Protect remaining fields of `struct pipe' using the pipe_lock. In orderanton
to simplify the locking pattern, revert back to using a hand-rolled I/O lock just like FreeBSD and NetBSD does. The state of pipes is quite different compared to when I made use of a rwlock for the I/O lock in revision 1.96. Most notably, the pipe_lock can now be used while sleeping. This does imply that witness(4) tracking of the I/O lock is lost but the implementation ends up being simpler. ok visa@
2019-12-25TIMEOUT_INITIALIZER(9): C99 initializerscheloha
2019-12-25timeout(9): new flag: TIMEOUT_SCHEDULED, new statistic: tos_scheduledcheloha
This flag is set whenever a timeout is put on the wheel and cleared upon (a) running, (b) deletion, and (c) readdition. It serves two purposes: 1. Facilitate distinguishing scheduled and rescheduled timeouts. When a timeout is put on the wheel it is "scheduled" for a later softclock(). If this happens two or more times it is also said to be "rescheduled". The tos_rescheduled value thus indicates how many distant timeouts have been cascaded into a lower wheel level. 2. Eliminate false late timeouts. A timeout is not late if it is due before softclock() has had a chance to schedule it. To track this we need additional state, hence a new flag. rprocter@ raises some interesting questions. Some answers: - This interface is not stable and name changes are possible at a later date. - Although rescheduling timeouts is a side effect of the underlying implementation, I don't forsee us using anything but a timeout wheel in the future. Other data structures are too slow in practice, so I doubt that the concept of a rescheduled timeout will be irrelevant any time soon. - I think the development utility of gathering these sorts of statistics is high. Watching the distribution of timeouts under a given workflow is informative. ok visa@
2019-12-24delete a few sentences which only restate what is already obvious;Ingo Schwarze
OK jmc@ deraadt@ kn@
2019-12-24Remove non-sensical line. The node certainly hasn't been rebuilt yet,Marc Espie
and the first thing job_attach_node does is... set the field to BUILDING. probably remnants of code prior to refactoring okay captain_obvious
2019-12-24dmesg(8) allocated a bit too much memory due to padding of structAlexander Bluhm
msgbuf. Use the same size algorithm in kernel and userland. OK cheloha@ guenther@ deraadt@
2019-12-24Fill in names for consbufsize and consbuf sysctl for nicer kdump(1)Alexander Bluhm
output.
2019-12-24Merge two missed fixes from login.c to login_passwd.c.Todd C. Miller
- use the correct length when checking for "-v lastchance=yes" - don't try to zero pass if it is NULL From miod@
2019-12-24The console buffer is allocated during startup. initconsbuf() isAlexander Bluhm
only called from main(). There allocation must not fail, so better use M_WAITOK and remove error handling. As it is not a temporary buffer, M_TTYS is more appropriate. OK deraadt@ mpi@
2019-12-24simplify assertionsanton
2019-12-24Fix name of option, GitHub issue 2030.Nicholas Marriott
2019-12-24add pipe kqueue testsanton
2019-12-24regenVisa Hankala
2019-12-24Unlock nanosleep(2).Visa Hankala
OK cheloha@, anton@, mpi@
2019-12-23fix broken tree. sorry for inconveniences.Alexandr Nedvedicky
2019-12-23rdr-to with loopback destination should work even thoughAlexandr Nedvedicky
IP forwarding is disabled. Issue reported by Daniel Jakots (danj@) OK bluhm@
2019-12-23Machines with many CPUs and long feature lists fill up the dmesg(8)Alexander Bluhm
during kernel startup before syslogd(8) can receive it. Increase message buffer size from 94k to 128k on amd64. reported by Hrvoje Popovski; OK deraadt@
2019-12-23syncTheo de Raadt
2019-12-23Link ospf6d regress testdenis
2019-12-23Add basic regress test for ospf6d.denis
OK benno@ remi@ and comment by claudio@
2019-12-23Ralph Dolmans from nlnetlabs points out that libunbound usesFlorian Obser
ub_event_pluggable.c instead of ub_event.c. ( https://github.com/NLnetLabs/unbound/issues/99 ) We have been the odd one out, so switch to ub_event_pluggable, too.
2019-12-23The boot loader allows to inspect memory with the hexdump command.Alexander Bluhm
Document the new feature in boot(8) man page. OK jmc@ deraadt@
2019-12-23Log a warning when a neighbor changes its address.remi
Same as ospfd's hello.c rev 1.23. ok denis@
2019-12-23when aggr(4) comes up, check port link state to push the rxm forward.David Gwynne
this lets aggr come up on boot if there's a race with it being brought up and the ports being up. reported by holger glaess on misc@ and debugged with hrvoje popovski. tested by hrvoje popovski too.
2019-12-23Add amdgpio(4), a driver for the GPIO controller found on newer AMDMark Kettenis
AMD SoCs/chipsets. From James Hastings
2019-12-23Area is now part of struct ifacedenis
OK remi@
2019-12-23Teach gdb that the trap frame should be used for alltraps_kern_meltdown().YASUOKA Masahiko
ok bluhm kettenis
2019-12-23Fix typo "off" -> "of"kmos
From Lev Lazinskiy Thanks!
2019-12-22midi(4): *sleep(9) -> *sleep_nsec(9)cheloha
These are straightforward except for the tsleep(9) conversion. ratchov@ had a bit to say about that code: https://marc.info/?l=openbsd-tech&m=157665936017373&w=2 > The problem is that close(2) may reset the transmitter before the few > bytes of its internal buffer is sent on the wire; there's no "wait for > completion" feature in such simple hardware, so we just wait few > milliseconds. > > The transmitter buffer size is around 16 bytes, the byte rate is 3125 > bytes/second. So if we wait at least 16B / 3125B/s = 5.12ms, we're > safe. Waiting 10ms-20ms is enough and is unnoticeable. Hence, in this diff we wait a flat 20ms in that situation. ok ratchov@
2019-12-22regenMark Kettenis
2019-12-22Wire up ipmi(4).Mark Kettenis
ok deraadt@
2019-12-22- give a specific value to OP_ERROR that doesn't occur in natureMarc Espie
- define OP_ZERO as zero, to make some function calls obvious - split ParseDoOp into two functions: ParseDoOp that only deals with : :: ! and ParseDoSpecial that only deals with special nodes. This simplifies both functions accordingly - always initialize special_op okay millert@
2019-12-22Scale send buffer on socket.denis
OK remi@
2019-12-22code cleanup and rearranging. no intentionnal behaviour change (except a ↵Sebastien Marie
printf(3) changed to warn(3)) fine deraadt@
2019-12-22Rename and move calc_nexthop_clear()/calc_nexthop_add()denis
OK claudio@
2019-12-22we also have "VAR_*" constants in parsevar with totally different meanings.Marc Espie
Rename to avoid ambiguity - VAR_IS_SHELL (in var.c): the SHELL variable, which has specific POSIX semantics - VAR_SHELL (in parsevar.c): assign the result of running the command to the variable. no actual code change
2019-12-22turns out I did fix the POSIX behavior of SHELL a while back.Marc Espie
The test was just slightly bogus, as SHELL should be put *before* make.
2019-12-22Add regression test for ftpd(8).jan
OK bluhm@
2019-12-22have parseb64file be non-destructive, so we can write theMarc Espie
comment in zsig without needing an extra copy okay tedu@
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-27 10:23:07 +0000