summaryrefslogtreecommitdiffstats
path: root/lib/libpthread/thread/thr_read.c
Commit message (Collapse)AuthorAgeFilesLines
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add RCS IDs to those files without them.deischen1999-08-051-2/+2
| | | | | | | Fix copyrights (s/REGENTS/AUTHOR). Suggested by: tg Approved by: jb
* Check the access mode in the flags before waiting on a read or a writejb1998-06-101-1/+13
| | | | | that might never be possible if the file was not opened in the corrent mode. This prevents a hang for bad programs. Why do people code like that?
* Implement compile time debug support instead of tracking file name andjb1998-06-091-4/+7
| | | | | | | line number every time a file descriptor is locked. This looks like a big change but it isn't. It should reduce the size of libc_r and make it run slightly faster.
* Change signal model to match POSIX (i.e. one set of signal handlersjb1998-04-291-4/+3
| | | | | | | | | | | | | | | | | | | | for the process, not a separate set for each thread). By default, the process now only has signal handlers installed for SIGVTALRM, SIGINFO and SIGCHLD. The thread kernel signal handler is installed for other signals on demand. This means that SIG_IGN and SIG_DFL processing is now left to the kernel, not the thread kernel. Change the signal dispatch to no longer use a signal thread, and call the signal handler using the stack of the thread that has the signal pending. Change the atomic lock method to use test-and-set asm code with a yield if blocked. This introduces separate locks for each type of object instead of blocking signals to prevent a context switch. It was this blocking of signals that caused the performance degradation the people have noted. This is a *big* change!
* Add parentheses to make blocking mode work.jb1997-04-011-1/+3
|
* Submitted by: John Birrelljulian1997-02-051-15/+22
| | | | uthreads update from the author.
* Reviewed by: julianjulian1996-01-221-0/+74
Submitted by: john birrel One version of the pthreads library another will follow with differnt actions under some cases.. not QUITE complete
OpenPOWER on IntegriCloud