[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <456223AC.5080400@redhat.com>
Date: Mon, 20 Nov 2006 13:52:44 -0800
From: Ulrich Drepper <drepper@...hat.com>
To: Jeff Garzik <jeff@...zik.org>
CC: Evgeniy Polyakov <johnpol@....mipt.ru>,
David Miller <davem@...emloft.net>,
Andrew Morton <akpm@...l.org>, netdev <netdev@...r.kernel.org>,
Zach Brown <zach.brown@...cle.com>,
Christoph Hellwig <hch@...radead.org>,
Chase Venters <chase.venters@...entec.com>,
Johann Borck <johann.borck@...sedata.com>,
linux-kernel@...r.kernel.org, Alexander Viro <aviro@...hat.com>
Subject: Re: [take24 0/6] kevent: Generic event handling mechanism.
Jeff Garzik wrote:
> I think we have lived with relative timeouts for so long, it would be
> unusual to change now. select(2), poll(2), epoll_wait(2) all take
> relative timeouts.
I'm not talking about always using absolute timeouts.
I'm saying the timeout parameter should be a struct timespec* and then
the flags word could have a flag meaning "this is an absolute timeout".
I.e., enable both uses,, even make relative timeouts the default.
This is what the modern POSIX interfaces do, too, see clock_nanosleep.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
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/
Powered by blists - more mailing lists