linux-kernel - Re: [RFC] schedule_timeout

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 21 Jul 2008 21:33:27 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC] schedule_timeout_range()

On Tue, 22 Jul 2008 13:56:29 +1000
Nick Piggin <nickpiggin@...oo.com.au> wrote:

> Rather than specific "deadline" values (which we can't guarantee
> anyway), or vague "can defer" values, I would prefer just a small
> selection of maybe orders of magnitude flags, maybe SECONDS,
> MILLISECONDS, MICROSECONDS which gives an amount of delay the kernel
> might add to the timer.

the problem is that many of these are "I'd like a timeout between 30
and ..eh 40 seconds" (think scsi timeouts or networkcard timeouts)

it's not just specific slack units.

> 
-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/