Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Feb 2003 18:45:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Feb 2003 18:45:09 -0500 Received: from x35.xmailserver.org ([208.129.208.51]:24709 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id ; Fri, 14 Feb 2003 18:43:03 -0500 X-AuthUser: davidel@xmailserver.org Date: Fri, 14 Feb 2003 16:00:03 -0800 (PST) From: Davide Libenzi X-X-Sender: davide@blue1.dev.mcafeelabs.com To: Linus Torvalds 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: 1165 Lines: 35 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 ? > but since the infrastructure is hopefully identical (most of the sigfd() > code is actually creating the fs infrastructure to get an inode with the > information), it should share a lot of the paths. About that, I think we should make an utility function to be shared among all the code that need to create "fake" inodes to expose fds. Right now many component ( pipes, futexes, epoll, ... ) uses the basic code, sharing the same needs, and duplicating basically the same code. - 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/