From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 4 18:00:25 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D7B10656A6; Fri, 4 Feb 2011 18:00:25 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5EA6F8FC22; Fri, 4 Feb 2011 18:00:12 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p14I0BPb038167; Fri, 4 Feb 2011 11:00:11 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p14I0BOY038166; Fri, 4 Feb 2011 11:00:11 -0700 (MST) (envelope-from ken) Date: Fri, 4 Feb 2011 11:00:11 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110204180011.GA38067@nargothrond.kdm.org> References: <20110113203750.GA39494@nargothrond.kdm.org> <20110114001758.GA12793@nargothrond.kdm.org> <07392102-4584-4690-9188-5202728CC7CA@tingvold.com> <20110120155746.GA22515@nargothrond.kdm.org> <070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com> <20110203221056.GA25389@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2011 18:00:26 -0000 On Fri, Feb 04, 2011 at 14:50:34 +0100, Joachim Tingvold wrote: > On Thu, Feb 03, 2011, at 23:10:56PM GMT+01:00, Kenneth D. Merry wrote: > >Try running this, and then do 'sysctl hw.mps' and let's see what > >your low > >water mark is for free chain elements. We'll also want to make sure > >your > >chain_free value is about equal to MPS_CHAIN_FRAMES when the system is > >idle. On my system with a LSI 9201-16i controller, I see: > > While idle; > > [jocke@filserver ~]$ sysctl hw.mps.0 > hw.mps.0.debug_level: 0 > hw.mps.0.allow_multiple_tm_cmds: 0 > hw.mps.0.io_cmds_active: 0 > hw.mps.0.io_cmds_highwater: 53 > hw.mps.0.chain_free: 2048 > hw.mps.0.chain_free_lowwater: 2029 > hw.mps.0.chain_alloc_fail: 0 > > After I copied a 22G file from 'storage' to 'zroot'; > > [jocke@filserver ~]$ sysctl hw.mps.0 > hw.mps.0.debug_level: 0 > hw.mps.0.allow_multiple_tm_cmds: 0 > hw.mps.0.io_cmds_active: 0 > hw.mps.0.io_cmds_highwater: 99 > hw.mps.0.chain_free: 2048 > hw.mps.0.chain_free_lowwater: 2029 > hw.mps.0.chain_alloc_fail: 0 > > After I copied a 22G file from 'zroot' to 'storage'; > > [jocke@filserver ~]$ sysctl hw.mps.0 > hw.mps.0.debug_level: 0 > hw.mps.0.allow_multiple_tm_cmds: 0 > hw.mps.0.io_cmds_active: 0 > hw.mps.0.io_cmds_highwater: 897 Looks like there were a lot of commands active at once. > hw.mps.0.chain_free: 2048 > hw.mps.0.chain_free_lowwater: 2029 > hw.mps.0.chain_alloc_fail: 0 But no more than 19 chain elements used at any one time. Perhaps it could depend on memory fragmentation somewhat. Over time you may see the low water mark go down a bit. The good news is that it doesn't look like we have a leak. Ken -- Kenneth Merry ken@FreeBSD.ORG