From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 18 04:03:57 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5FB23A77; Fri, 18 Jan 2013 04:03:57 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-ia0-x234.google.com (mail-ia0-x234.google.com [IPv6:2607:f8b0:4001:c02::234]) by mx1.freebsd.org (Postfix) with ESMTP id 1D86FA56; Fri, 18 Jan 2013 04:03:57 +0000 (UTC) Received: by mail-ia0-f180.google.com with SMTP id f27so1025526iae.25 for ; Thu, 17 Jan 2013 20:03:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=gda+puCNeEMZMr7iLaneuVyh8P39v7nV9e5VCKfIBL4=; b=Ai4sAax/xWpX8nVqNRNnsczihhQp2F3ia6dB0syc/45F/vplmcdAwvTR0q03IVT2bX lVfDUV6gTnsLpVX5a/ILzN72rcr3B2/ujB3jShinPFOzTcl5vb4kgWE+qhjx1hlpH12p nix1il2P2/8FQ/XiMrWjm3lNUaZFkIz0u7P8T+VzjVusXrwnXRF18pNGqe36x7BhIsRS 8bX2oXDxBK4dNsOquXwXcmMDJM8wrXq2zjWX37QyAhGrFwy0QyFzRyAN4xzHFgr4Ux5O ViytJCvoG6HL1X5r6aOfudeVQgGHWYRkErfPdosDILWDCgzunURige+BR9fDpnUBEiCP 7Beg== MIME-Version: 1.0 X-Received: by 10.50.159.165 with SMTP id xd5mr946901igb.82.1358481836890; Thu, 17 Jan 2013 20:03:56 -0800 (PST) Received: by 10.64.107.196 with HTTP; Thu, 17 Jan 2013 20:03:56 -0800 (PST) Date: Thu, 17 Jan 2013 20:03:56 -0800 Message-ID: Subject: Re: IBM blade server abysmal disk write performances From: Dieter BSD To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: gibbs@FreeBSD.org, scottl@FreeBSD.org, mjacob@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 04:03:57 -0000 > I am thinking that something fancy in that SAS drive is > not being handled correctly by the FreeBSD driver. I think so too, and I think the something fancy is "tagged command queuing". The driver prints "da0: Command Queueing enabled" and yet your SAS drive is only getting 1 write per rev, and queuing should get you more than that. Your SATA drive is getting the expected performance, which means that NCQ must be working. > Please let me know if there is anything you would like me to run on the > BSD 9.1 system to help diagnose this issue? Looking at the mpt driver, a verbose boot may give more info. Looks like you can set a "debug" device hint, but I don't see any documentation on what to set it to. I think it is time to ask the driver wizards why TCQ isn't working, so I'm cc-ing the authors listed on the mpt man page.