From owner-freebsd-stable@FreeBSD.ORG Mon Mar 23 00:31:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8244810656BD; Mon, 23 Mar 2009 00:31:16 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (unknown [IPv6:2001:380:e06:127::53]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8338FC1A; Mon, 23 Mar 2009 00:31:15 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id E27D578C4B; Mon, 23 Mar 2009 09:31:14 +0900 (JST) Received: from artemis (unknown [192.168.2.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTP id B95DC78C4A; Mon, 23 Mar 2009 09:31:14 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: Date: Mon, 23 Mar 2009 09:31:12 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: istgt now supports command queuing in disk type X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 00:31:20 -0000 Hello. New release was uploaded in my blog. The command queuing improves especially sequential read by MCS(multiple connections per session) round robin. In my post, I uploaded the screen shots using CrystalDiskMark which is one of popular benchmark in Japan. You can download CrystalDiskMark(multilingual) from: http://crystalmark.info/?lang=en I got the result about 1.5x-3x faster than previous 20090314. If test data was cached, it reached over 200MB/s. Known Issue and Limitations: o queuing is only supported in single initiator environment. o LUN thread might have deadlock when an error has occurred. o write command is still slow. o timeout may occur when using MCS. o single connection may be slower than without queuing. Here is release 20090323: http://shell.peach.ne.jp/aoyama/archives/376 The screen shots show difference between QueueDepth 16 and 0 (disabled queuing). The command queuing is disabled by default. If you want to use it, please add QueueDepth key in the LogicalUnit section of your configuration. for example: [LogicalUnit1] # Queuing 0=disabled, 1-255=enabled with specified depth. QueueDepth 16 Thanks. -- Daisuke Aoyama