"65343c78" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"65343 c78" (Results 1 – 3 of 3) sorted by relevance

/freebsd/sys/sys/
H A D	posix4.h	65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes.
/freebsd/sys/kern/
H A D	p1003_1b.c	65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes.
H A D	ksched.c	65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes. 65343c78 Tue Jul 11 06:11:34 GMT 2006 David Xu <davidxu@FreeBSD.org> Extended the POSIX scheduler APIs to accept lwpid as well, we've already done this in ptrace syscall, when a pid is large than PID_MAX, the syscall will search a thread in current process. It permits 1:1 thread library to get and set a thread's scheduler attributes.