linux-kernel - Re: Tickles 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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1010281317270.26782@router.home>
Date:	Thu, 28 Oct 2010 13:18:41 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Mark Hounschell <markh@...pro.net>
cc:	Dragoslav Zaric <zaricdragoslav@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Tickles scheduler

On Thu, 28 Oct 2010, Mark Hounschell wrote:

> On 10/28/2010 09:47 AM, Christoph Lameter wrote:
> > The current plan is to switch off the tick when a process is running that
> > cannot be preempted ("realtime" (very bad choice of terms) tasks).
> >
>
> In what kind of time frame is this plan? And in the plan what will be the criteria for
> "cannot be preempted"?

Time frame is dependent on my available time unless someone else steps
forward to help out. The criteria for "cannot be preempted" could be
initially a process running with SCHED_FIFO.
--
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/