From owner-freebsd-net@FreeBSD.ORG Fri Oct 22 18:07:50 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F333316A4CE for ; Fri, 22 Oct 2004 18:07:49 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9707B43D4C for ; Fri, 22 Oct 2004 18:07:49 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i9MI7mqw039924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Fri, 22 Oct 2004 14:07:48 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i9MI7m0O039921; Fri, 22 Oct 2004 14:07:48 -0400 (EDT) (envelope-from wollman) Date: Fri, 22 Oct 2004 14:07:48 -0400 (EDT) From: Garrett Wollman Message-Id: <200410221807.i9MI7m0O039921@khavrinen.lcs.mit.edu> To: "Ronald F. Guilmette" In-Reply-To: <2171.1098468090@monkeys.com> References: <20041022172759.GX22681@funkthat.com> <2171.1098468090@monkeys.com> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 cc: freebsd-net@FreeBSD.ORG Subject: Re: aio_connect ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 18:07:50 -0000 < said: > Signal numbers are typically represented as ints. Is there anything in > the kernel that prevents me from, say, calling kill(2) with a second > argument of, say, 0xdeadbeef, in other words any old random int value > that I might care to use? Yes. Signals are represented, in the kernel and in the API, as bits in fixed-size bitmaps. POSIX real-time signals, if we implemented them, would at least give you the opportunity to queue signals, with unique ancillary data attached to each instance. We have all the mechanism to do this in the user-kernel interface; it's just not implemented in the kernel. -GAWollman