From owner-freebsd-current Fri Jan 10 2:57:54 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E9A37B401; Fri, 10 Jan 2003 02:57:53 -0800 (PST) Received: from smtp03.iprimus.com.au (smtp03.iprimus.com.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 101B243EB2; Fri, 10 Jan 2003 02:57:52 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from smtp02.iprimus.net.au (210.50.76.70) by smtp03.iprimus.com.au (6.7.010) id 3E0FA3A2000FCFC1; Fri, 10 Jan 2003 21:57:45 +1100 Received: from dilbert.robbins.dropbear.id.au ([210.50.40.74]) by smtp02.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600); Fri, 10 Jan 2003 21:57:41 +1100 Received: from dilbert.robbins.dropbear.id.au (61q93qbu43qclrub@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6) with ESMTP id h0AAvblk031851; Fri, 10 Jan 2003 21:57:39 +1100 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6/Submit) id h0AAvbmi031850; Fri, 10 Jan 2003 21:57:37 +1100 (EST) (envelope-from tim) Date: Fri, 10 Jan 2003 21:57:36 +1100 From: Tim Robbins To: Juli Mallett Cc: current@FreeBSD.org, re@FreeBSD.org Subject: Re: Serious issues with kqueue on sockets on CURRENT. Message-ID: <20030110215736.A31727@dilbert.robbins.dropbear.id.au> References: <20030110013015.A23399@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030110013015.A23399@FreeBSD.org>; from jmallett@FreeBSD.org on Fri, Jan 10, 2003 at 01:30:16AM -0800 X-OriginalArrivalTime: 10 Jan 2003 10:57:42.0229 (UTC) FILETIME=[19354850:01C2B897] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jan 10, 2003 at 01:30:16AM -0800, Juli Mallett wrote: > Lately, the data field for sockets, which holds bytes ready (in the EVFILT_ > READ case) to be read, is computed to be zero. This means that if you have > a low watermark which is >0 per the kq, THE EVENT WILL NEVER HAPPEN. Not to > mention that this means when the event IS triggered properly (if you can > call it that), it is always said to have =ZERO= bytes ready. [...] I can definitely reproduce this here and also fairly angry about it. In addition to what you mentioned, fstat() gives an incorrect st_size result now and it's likely that non-NOTE_LOWAT low watermarks are firing too early as well. Ugly test program @ http://people.freebsd.org/~tjr/kq.c Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message