Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Feb 2003 18:56:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Feb 2003 18:56:49 -0500 Received: from mail.zmailer.org ([62.240.94.4]:42390 "EHLO mail.zmailer.org") by vger.kernel.org with ESMTP id ; Fri, 14 Feb 2003 18:56:40 -0500 Date: Sat, 15 Feb 2003 02:06:28 +0200 From: Matti Aarnio To: Davide Libenzi Cc: Linus Torvalds , Kernel Mailing List Subject: Re: Synchronous signal delivery.. Message-ID: <20030215000628.GB1073@mea-ext.zmailer.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1164 Lines: 30 On Fri, Feb 14, 2003 at 04:00:03PM -0800, Davide Libenzi wrote: > On Thu, 13 Feb 2003, Linus Torvalds wrote: .... > > > > One of the reasons for the "flags" field (which is not unused) was because > > > > I thought it might have extensions for things like alarms etc. > > > I was thinking more like : > > > > > > int timerfd(int timeout, int oneshot); > > > > It could be a separate system call, ... > > I would personally like it a lot to have timer events available on > pollable fds. Am I alone in this ? Somehow all this idea has a feeling of long established Linux kernel facility called: netlink It can send varying messages to userspace via a file-handle, and is pollable. Originally that is for network codes, and therefore it already has protocol capable to handle multiple different formats, handle queue saturation, etc. Do we need new syscall(s) ? Could it all be done with netlink ? /Matti Aarnio - 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/