Re: allow non root users to set io priority "idle" ?

Sheplyakov Alexei
2007-08-08T11:50:08Z

[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]

On Wed, Aug 08, 2007 at 12:20:56PM +0200, Andi Kleen wrote:

> > I don't quite understand. There are a lot of other ways to starve such
> > high-priority process:
> > 1. renice the low-priority process
>
> That requires user action.

As well as lowering IO priority.

> > 2. send it a signal
> > 3. ptrace it
>
> Only root can do these.

The original question (unless I'm missing something) was "why _the owner_
of a process is not enabled to lower its IO priority?" The owner of the
process certainly can send signal and ptrace it.

> Low priority as allowed by renice is ok -- the resource holder will
> run eventually and the system make progress.

System (whatever that means) should not depend on random users' processes.

> e.g. if you google a bit you can find a famous story where the NASA
> had to do that remotely to solve a PI problem on one of the Mars rovers.

Certainly there are a scenarios when lowering priority (CPU or IO) have
negative effect. "If it hurts -- then don't do it". However, it is not
kernels job to decide if the user is right. If the user asks to do
something "stupid" (run his process with idle IO priority, whipe out his
home directory, you name it) -- just do that (as long as the action is
permitted by the security policy).

P.S.
Please CC me, I'm not subscribed.

Best regards,
Alexei

--
All science is either physics or stamp collecting.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]