From owner-freebsd-hackers Thu Aug 23 17:47:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 56CC737B408 for ; Thu, 23 Aug 2001 17:47:35 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f7O0lWX41062; Thu, 23 Aug 2001 17:47:32 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.5/8.11.0) id f7O0lWm01329; Thu, 23 Aug 2001 17:47:32 -0700 (PDT) (envelope-from jdp) Date: Thu, 23 Aug 2001 17:47:32 -0700 (PDT) Message-Id: <200108240047.f7O0lWm01329@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: julian@elischer.org Subject: Re: Kernel level inet socket handling In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Julian Elischer wrote: [concerning my fixes for ng_ksocket nodes to handle TCP operations] > If you send me the files I can diff them and commit them. > (of course you are welcome to do it yourself at your own pace if you wish) Hmm, I just might take you up on that. :-) The biggest obstacle is that I have been working on the -stable branch, so the changes will have to be made compatible with -current. I know you added some locking in -current, but I had the impression that it's fairly well hidden from most nodes. Is that right? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message