linux-kernel - Re: Questions about linux scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <292693080910300320q1857cc70s73eb524c34af8233@mail.gmail.com>
Date:	Fri, 30 Oct 2009 15:50:15 +0530
From:	Daniel Rodrick <daniel.rodrick@...il.com>
To:	Chris Friesen <cfriesen@...tel.com>
Cc:	Linux Newbie <linux-newbie@...r.kernel.org>,
	Kernel Newbies <kernelnewbies@...linux.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Questions about linux scheduler

Hi,

>
>> * A lower priority process will run only if there are no runnable
>> processes in priority above it - this automatically means that all RT
>> processes get to run before non-RT processes.
>
> True for RT, not true for non-RT.  In the current scheduler the non-RT
> tasks are stored in a time-ordered structure rather than the 40
> runqueues that were used before.  A non-RT task will run once it becomes
> the most "urgent" task based on its nice level, how much cpu time it
> uses, and how long it's been since it ran last relative to other tasks
> on the system.

One last question ... the nice value of a process never changes
(unless done explicitly using nice system call), right?

Thanks,

Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/