From owner-freebsd-chat Thu Oct 26 18:33: 1 2000 Delivered-To: freebsd-chat@freebsd.org Received: from the-village.bc.nu (lightning.swansea.linux.org.uk [194.168.151.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B80E37B479 for ; Thu, 26 Oct 2000 18:32:59 -0700 (PDT) Received: from alan by the-village.bc.nu with local (Exim 2.12 #1) id 13oyOE-00044z-00; Fri, 27 Oct 2000 02:33:02 +0100 Subject: Re: kqueue microbenchmark results To: jlemon@flugsvamp.com (Jonathan Lemon) Date: Fri, 27 Oct 2000 02:32:59 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), jlemon@flugsvamp.com (Jonathan Lemon), gid@cisco.com (Gideon Glass), sim@stormix.com (Simon Kirby), dank@alumni.caltech.edu (Dan Kegel), chat@freebsd.org, linux-kernel@vger.kernel.org In-Reply-To: <20001026201042.A38500@prism.flugsvamp.com> from "Jonathan Lemon" at Oct 26, 2000 08:10:42 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > the application of a close event. What can I say, "the fd formerly known > as X" is now gone? It would be incorrect to say that "fd X was closed", > since X no longer refers to anything, and the application may have reused > that fd for another file. Which is precisely why you need to know where in the chain of events this happened. Otherwise if I see 'read on fd 5' 'read on fd 5' How do I know which read is for which fd in the multithreaded case > As for the multi-thread case, this would be a bug; if one thread closes > the descriptor, the other thread is going to get an EBADF when it goes > to perform the read. Another thread may already have reused the fd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message