From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 15:50:42 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 8C1451065672; Mon, 21 Feb 2011 15:50:42 +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 124998FC08; Mon, 21 Feb 2011 15:50:41 +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 p1LFoftR038062; Mon, 21 Feb 2011 08:50:41 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p1LFof2d038061; Mon, 21 Feb 2011 08:50:41 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2011 08:50:41 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110221155041.GA37922@nargothrond.kdm.org> References: <070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com> <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> 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: Mon, 21 Feb 2011 15:50:42 -0000 On Sun, Feb 20, 2011 at 04:10:19 +0100, Joachim Tingvold wrote: > On Fri, Feb 18, 2011, at 18:16:19PM GMT+01:00, Kenneth D. Merry wrote: > >I just committed a fix to -current for the out of chain buffers > >issue. If > >you've got time, pull that fix in and see whether it works for you. > > [jocke@filserver /storage/tmp]$ i=0;while [ $i -le 10 ]; do dd if=/ > dev/zero of=foo bs=1M count=204800; let "i += 1"; done > > I let it run for a while, and checked back later. > > > > 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: 970 > hw.mps.0.chain_free: 1024 > hw.mps.0.chain_free_lowwater: 0 > hw.mps.0.chain_alloc_fail: 786 > > As you can see, I didn't do anything about the 'MPS_CHAIN_FRAMES'- > value after I pulled the latest version. I could change it, but I > guess this only would get rid of the 'out of chain'-messages, and not > really solve the underlying problem. Okay, good. It looks like it is running as designed. I'll probably just double the number of chain buffers and disable the messages. >From previous experiments, the problem is much less likely to occur when you have 2048 chain buffers, correct? What filesystem are you using by the way? Ken -- Kenneth Merry ken@FreeBSD.ORG