Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Feb 2003 17:14:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Feb 2003 17:14:29 -0500 Received: from x35.xmailserver.org ([208.129.208.51]:42382 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id ; Sat, 15 Feb 2003 17:14:28 -0500 X-AuthUser: davidel@xmailserver.org Date: Sat, 15 Feb 2003 14:31:37 -0800 (PST) From: Davide Libenzi X-X-Sender: davide@blue1.dev.mcafeelabs.com To: James Antill cc: Kernel Mailing List Subject: Re: Synchronous signal delivery.. In-Reply-To: Message-ID: References:

MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1101 Lines: 30 On Sat, 15 Feb 2003, James Antill wrote: > > I would personally like it a lot to have timer events available on > > pollable fds. Am I alone in this ? > > Think of "timer events" as a single TCP connection, so you have... > > time X: empty > time X+Y: timed event "Arrives" > time X+Z: timed event "Arrives" > > ...at which point it's pretty obvious that if you "poll" the timer > event queue from anytime before X+Y it'll be empty, and anytime after > X+Y it'll be "full". There isn't any point in being able to distinguish > between the events X+Y and X+Z, you only need to know a timed event has > occurred so you should process all timed events that are needed. > At which point you just need to work out the difference between X and > X+Y, and pass that to poll/sigtimedwait/etc. I'm sorry, I'm a bit confused. What's the point here ? - Davide - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/