Ian Dowse 4784a46912 Replace the code for reading and writing the kernel message buffer ... with a new implementation that has a mostly reentrant "addchar" routine, supports multiple message buffers in the kernel, and hides the implementation details from callers. The new code uses a kind of sequence number to represend the current read and write positions in the buffer. This approach (suggested mainly by bde) permits the read and write pointers to be maintained separately, which reduces the number of atomic operations that are required. The "mostly reentrant" above refers to the way that while it is now always safe to have any number of concurrent writers, readers could see the message buffer after a writer has advanced the pointers but before it has witten the new character. Discussed on: freebsd-arch		2003-06-22 02:18:31 +00:00
..
dmesg.8	s/filesystem/file system/g as discussed on -developers	2002-08-21 18:11:48 +00:00
dmesg.c	Replace the code for reading and writing the kernel message buffer	2003-06-22 02:18:31 +00:00
Makefile	These are WARNS=2 clean, try to keep them that way.	2003-02-23 13:25:02 +00:00