Date: Fri, 10 Jan 2003 21:57:36 +1100 From: Tim Robbins <tjr@FreeBSD.org> To: Juli Mallett <jmallett@FreeBSD.org> 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> In-Reply-To: <20030110013015.A23399@FreeBSD.org>; from jmallett@FreeBSD.org on Fri, Jan 10, 2003 at 01:30:16AM -0800 References: <20030110013015.A23399@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030110215736.A31727>