Chandra Seetharaman wrote:
Resource Groups(CKRM) does allow threads to be in different Resource
Groups ( and since Resource Group assignment is dynamic, a thread can
move to a high priority resource group for a specific operation and get
back to its original resource group after the operation is complete).
Just wondering if that is sufficient or you _would_ need support from
NPTL.
The main issue is that the mapping between pthread_t and and PID is only
known by NPTL. A thread can find it's own PID (for purposes of resource
groups) but it can't find the PID of other threads given their pthread_t.
Essentially I'm looking for cpu-group equivalents to:
pthread_setschedparam()
pthread_getschedparam()
pthread_attr_setschedpolicy()
pthread_attr_getschedpolicy()
It's not absolutely critical, but we did add it to our current NPTL.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
