linux-kernel - Re: [patch 0/5] Nano/Microsecond resolution for select() and poll()

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]

Date:	Fri, 29 Aug 2008 15:15:34 -0700 (PDT)
From:	Brian Wellington <bwelling@...ll.org>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...x.de,
	torvalds@...ux-foundation.org
Subject: Re: [patch 0/5] Nano/Microsecond resolution for select() and
 poll()

On Fri, 29 Aug 2008, Arjan van de Ven wrote:

> Today in Linux, select() and poll() operate in jiffies resolution
> (granularity), meaning an effective resolution of 1 millisecond (HZ=1000) to
> 10 milliseconds (HZ=100). Delays shorter than this are not possible, and all
> delays are in multiples of this granularity.

Would a similar change also be useful for epoll_wait()?  It's unfortunate
that there's no way to use epoll with more than millisecond granularity,
but it seems like the same arguments could be made as with poll().

Brian
--
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/