From owner-freebsd-arch@FreeBSD.ORG Fri Apr 16 19:53:55 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 294BB16A4CE; Fri, 16 Apr 2004 19:53:55 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id D544143D1F; Fri, 16 Apr 2004 19:53:54 -0700 (PDT) (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 i3H2rmXX021501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Fri, 16 Apr 2004 22:53: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 i3H2rmAV021500; Fri, 16 Apr 2004 22:53:48 -0400 (EDT) (envelope-from wollman) Date: Fri, 16 Apr 2004 22:53:48 -0400 (EDT) From: Garrett Wollman Message-Id: <200404170253.i3H2rmAV021500@khavrinen.lcs.mit.edu> To: green@freebsd.org In-Reply-To: <200404170212.i3H2Cg8n031749@green.homeunix.org> Organization: MIT Laboratory for Computer Science X-Spam-Score: -6.6 () IN_REP_TO,QUOTED_EMAIL_TEXT X-Scanned-By: MIMEDefang 2.37 cc: arch@freebsd.org Subject: Re: kqueue giant-locking (&kq_Giant, locking) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Apr 2004 02:53:55 -0000 In article <200404170212.i3H2Cg8n031749@green.homeunix.org> you write: >1. The recursion has been removed from kqueue. This means kqueues cannot be > added to other kqueues for EVFILT_READ -- yes, that ability has been > around since r1.1 of kern_event.c, Actually, I'm fairly certain that Jonathan considered this to be a fairly important property of kqueue and his papers do mention it. It was done that way specifically to allow a kqueue to be included in some larger application's event polling loop without needing to know how it was implemented. -GAWollman