From owner-freebsd-current@FreeBSD.ORG Sun Apr 2 23:40:13 2006 Return-Path: X-Original-To: current@FreeBSD.org 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 556EC16A401 for ; Sun, 2 Apr 2006 23:40:13 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECCEB43D45 for ; Sun, 2 Apr 2006 23:40:12 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4882A46B52; Sun, 2 Apr 2006 19:40:12 -0400 (EDT) Date: Mon, 3 Apr 2006 00:40:12 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: John Birrell In-Reply-To: <20060402230012.GA24758@what-creek.com> Message-ID: <20060403003428.X76562@fledge.watson.org> References: <20060317141627.W2181@fledge.watson.org> <20060329100839.V19236@fledge.watson.org> <20060401102918.P79188@fledge.watson.org> <20060401170554.R82503@fledge.watson.org> <20060402233436.P76562@fledge.watson.org> <20060402230012.GA24758@what-creek.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: HEADS UP: socket and pcb reference changes entering tree today X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 23:40:13 -0000 On Sun, 2 Apr 2006, John Birrell wrote: > I've just updated a current system which also serves as a (socket based) > backup system for a remotely hosted web site with LOTS of file updates. The > update went without a hitch and the system seems to work fine AFAICT. > > I guess that sounds like a bit of an anti-climax, but there really isn't > anything to report. Sorry. 8-) > > Perhaps I just don't know what to look for. Shrug. Well, other than the normal array of panics and bad network behavior, I'm particularly interested in possible memory leaks in the TCP and socket code. Generally speaking, I find the following useful for keeping an eye on it: vmstat -z | head -1 ; vmstat -z | grep -i tcp ; vmstat -z | grep -i socket Of course, because a lot of events and tear-downs in the network stack are asynchronous anyway, you have to watch for the leaks over a longer run time rather than the short term. Finally, I had some reports of additional connection resets from Kris during his testing, which may be tricky to track down if they still exist. Robert N M Watson