From owner-freebsd-current  Sun Jan 12  4:22:27 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 E654D37B401; Sun, 12 Jan 2003 04:22:25 -0800 (PST)
Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 82B6C43F1E; Sun, 12 Jan 2003 04:22:24 -0800 (PST)
	(envelope-from maxim@macomnet.ru)
Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14])
	by relay1.macomnet.ru (8.11.6/8.11.6) with ESMTP id h0CCLRG8566173;
	Sun, 12 Jan 2003 15:21:27 +0300 (MSK)
Date: Sun, 12 Jan 2003 15:21:26 +0300 (MSK)
From: Maxim Konovalov <maxim@macomnet.ru>
To: Kelly Yancey <kbyanc@posi.net>
Cc: Trish Lynch <trish@bsdunix.net>,
	"Daniel C. Sobral" <dcs@newsguy.com>, Peter Wemm <peter@wemm.org>,
	"" <current@FreeBSD.ORG>, "" <kbyanc@FreeBSD.ORG>
Subject: Re: Serious issues with kqueue on sockets on CURRENT.
In-Reply-To: <20030112034405.F27352-100000@gateway.posi.net>
Message-ID: <20030112151906.L98192@news1.macomnet.ru>
References: <20030112034405.F27352-100000@gateway.posi.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On 03:51-0800, Jan 12, 2003, Kelly Yancey wrote:

[...]

>   I'm sorry, I'm afraid I am not familiar with the issue being
> discussed.  Is there a PR I can reference for more information?
> Exactly what events aren't being received?  Being as the logic for
> when to return a kevent as of uipc_socket.c:1.136 is exactly the
> same as before (just the data value in the kevent is different), I
> can't see how any events could *not* be returned that weren't
> returned before.  But then again, without knowing the symptoms you
> are seeing, I can't say for sure.

Look at the top of the thread:

Juli's complain:

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=889789+0+archive/2003/freebsd-current/20030112.freebsd-current

Tim's test program and a patch:

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=889789+0+archive/2003/freebsd-current/20030112.freebsd-current

--
Maxim Konovalov, MAcomnet, Internet Dept., system engineer
phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message