Searched hist:232144 (Results 1 - 6 of 6) sorted by relevance
| /freebsd-11-stable/lib/libthr/thread/ | ||
| H A D | thr_umtx.c | diff 232209 Mon Feb 27 11:41:51 MST 2012 davidxu Follow changes made in revision 232144, pass absolute timeout to kernel, this eliminates a clock_gettime() syscall. diff 232144 Sat Feb 25 00:18:34 MST 2012 davidxu In revision 231989, we pass a 16-bit clock ID into kernel, however according to POSIX document, the clock ID may be dynamically allocated, it unlikely will be in 64K forever. To make it future compatible, we pack all timeout information into a new structure called _umtx_time, and use fourth argument as a size indication, a zero means it is old code using timespec as timeout value, but the new structure also includes flags and a clock ID, so the size argument is different than before, and it is non-zero. With this change, it is possible that a thread can sleep on any supported clock, though current kernel code does not have such a POSIX clock driver system. |
| H A D | thr_rwlock.c | diff 232209 Mon Feb 27 11:41:51 MST 2012 davidxu Follow changes made in revision 232144, pass absolute timeout to kernel, this eliminates a clock_gettime() syscall. |
| H A D | thr_umtx.h | diff 232209 Mon Feb 27 11:41:51 MST 2012 davidxu Follow changes made in revision 232144, pass absolute timeout to kernel, this eliminates a clock_gettime() syscall. |
| /freebsd-11-stable/lib/libc/gen/ | ||
| H A D | sem_new.c | diff 232144 Sat Feb 25 00:18:34 MST 2012 davidxu In revision 231989, we pass a 16-bit clock ID into kernel, however according to POSIX document, the clock ID may be dynamically allocated, it unlikely will be in 64K forever. To make it future compatible, we pack all timeout information into a new structure called _umtx_time, and use fourth argument as a size indication, a zero means it is old code using timespec as timeout value, but the new structure also includes flags and a clock ID, so the size argument is different than before, and it is non-zero. With this change, it is possible that a thread can sleep on any supported clock, though current kernel code does not have such a POSIX clock driver system. |
| /freebsd-11-stable/sys/kern/ | ||
| H A D | kern_umtx.c | diff 232209 Mon Feb 27 11:41:51 MST 2012 davidxu Follow changes made in revision 232144, pass absolute timeout to kernel, this eliminates a clock_gettime() syscall. diff 232144 Sat Feb 25 00:18:34 MST 2012 davidxu In revision 231989, we pass a 16-bit clock ID into kernel, however according to POSIX document, the clock ID may be dynamically allocated, it unlikely will be in 64K forever. To make it future compatible, we pack all timeout information into a new structure called _umtx_time, and use fourth argument as a size indication, a zero means it is old code using timespec as timeout value, but the new structure also includes flags and a clock ID, so the size argument is different than before, and it is non-zero. With this change, it is possible that a thread can sleep on any supported clock, though current kernel code does not have such a POSIX clock driver system. |
| /freebsd-11-stable/sys/sys/ | ||
| H A D | umtx.h | diff 232144 Sat Feb 25 00:18:34 MST 2012 davidxu In revision 231989, we pass a 16-bit clock ID into kernel, however according to POSIX document, the clock ID may be dynamically allocated, it unlikely will be in 64K forever. To make it future compatible, we pack all timeout information into a new structure called _umtx_time, and use fourth argument as a size indication, a zero means it is old code using timespec as timeout value, but the new structure also includes flags and a clock ID, so the size argument is different than before, and it is non-zero. With this change, it is possible that a thread can sleep on any supported clock, though current kernel code does not have such a POSIX clock driver system. |
Completed in 166 milliseconds