O(1) Entitlement Based Scheduler
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Mike Fedyk
Quoted 7 lines · Shailabh Nagar
Quoted 3 lines
Quoted 3 lines
Quoted 1 line · Mike Fedyk
Better would be to have the kernel tell the daemon whenever a process in exec-ed, and you have simplicity in the kernel, and policy in user space.
Quoted 4 lines
Quoted 1 line
As it turns out, one can still use a fairly simple in-kernel module which provides a *mechanism* for effectively changing a process' entitlement while retaining the policy component in userland.
How much code could be removed if CKRM triggered a userspace process to perform the operations required?
One other interesting question is what would happen if the userspace program didn't run, died, etc. Or set some ill-behaved other user program to a higher priority and the other program did a DoS (intentional or not)?
I don't like the whole idea, but I like it even less with a user program requiring context switches on scheduling.