Home | History | Annotate | Download | only in utils

Lines Matching refs:Thread

47      * A thread priority should be chosen inverse-proportionally to
48 * the amount of work the thread is expected to do. The more work
49 * a thread will do, the less favorable priority it should get so that
66 /* the main UI thread has a slightly more favorable priority */
94 // Create and run a new thread.
97 // Create thread with lots of parameters
105 // Get some sort of unique identifier for the current thread.
108 // Low-level thread creation -- never creates threads that can
131 // Get pid for the current thread.
134 // Change the scheduling group of a particular thread. The group
137 // the operation failed. Thread ID zero means current thread.
140 // Change the priority AND scheduling group of a particular thread. The priority
143 // in either case errno is set. Thread ID zero means current thread.
146 // Get the current priority of a particular thread. Returns one of the
150 // Get the current scheduling group of a particular thread. Normally returns
154 // Thread ID zero means current thread.
191 // Create and run a new thread.
196 // Create thread with lots of parameters
208 // Get some sort of unique identifier for the current thread.
218 * The mutex must be unlocked by the thread that locked it. They are not
219 * recursive, i.e. the same thread can't lock it multiple times.
315 * The mutex must be unlocked by the thread that locked it. They are not
316 * recursive, i.e. the same thread can't lock it multiple times.
422 // Signal the condition variable, allowing one thread to continue.
495 * This is our spiffy thread object!
498 class Thread : virtual public RefBase
501 // Create a Thread object, but doesn't create or start the associated
502 // thread. See the run() method.
503 Thread(bool canCallJava = true);
504 virtual ~Thread();
506 // Start the thread in threadLoop() which needs to be implemented.
511 // Ask this object's thread to exit. This function is asynchronous, when the
512 // function returns the thread might still be running. Of course, this
513 thread.
519 // Call requestExit() and wait until this object's thread exits.
521 // this function from this object's thread. Will return WOULD_BLOCK in
525 // Wait until this object's thread exits. Returns immediately if not yet running.
526 // Do not call from this object's thread; will return WOULD_BLOCK in that case.
534 // Derived class must implement threadLoop(). The thread starts its life
535 // here. There are two ways of using the Thread object:
538 // 2) once: if threadLoop() returns false, the thread will exit upon return.
542 Thread& operator=(const Thread&);
553 sp<Thread> mHoldSelf;