Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757956AbYBDNyA (ORCPT ); Mon, 4 Feb 2008 08:54:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754676AbYBDNxu (ORCPT ); Mon, 4 Feb 2008 08:53:50 -0500 Received: from wr-out-0506.google.com ([64.233.184.225]:39090 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754621AbYBDNxs (ORCPT ); Mon, 4 Feb 2008 08:53:48 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=wBg6+2cE5IYc7JVGu7M5yOZEJQ81Qd0MMuwrN1OHrAOkOLpTqRfSxrmAe8blLbZZ4NjIeCAXPPT4TLcKW2Chy3GEvbPFXEH8Dq1szp134JU2j+QHWmo3CSWt13xRAKXveOiQypkRTEb/WOyJgxh50IRNia9IbpVZsPkzgFwmRwk= Message-ID: Date: Mon, 4 Feb 2008 14:53:46 +0100 From: "Bart Van Assche" To: "Vladislav Bolkhovitin" Subject: Re: Integration of SCST in the mainstream Linux kernel Cc: "James Bottomley" , "Linus Torvalds" , "Andrew Morton" , "FUJITA Tomonori" , linux-scsi@vger.kernel.org, scst-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, "Nicholas A. Bellinger" In-Reply-To: <47A7049A.9000105@vlnb.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1201639331.3069.58.camel@localhost.localdomain> <47A05CBD.5050803@vlnb.net> <47A7049A.9000105@vlnb.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1888 Lines: 39 On Feb 4, 2008 1:27 PM, Vladislav Bolkhovitin wrote: > > So, James, what is your opinion on the above? Or the overall SCSI target > project simplicity doesn't matter much for you and you think it's fine > to duplicate Linux page cache in the user space to keep the in-kernel > part of the project as small as possible? It's too early to draw conclusions about performance. I'm currently performing more measurements, and the results are not easy to interpret. My plan is to measure the following: * Setup: target with RAM disk of 2 GB as backing storage. * Throughput reported by dd and xdd (direct I/O). * Transfers with dd/xdd in units of 1 KB to 1 GB (the smallest transfer size that can be specified to xdd is 1 KB). * Target SCSI software to be tested: IETD iSCSI via IPoIB, STGT iSCSI via IPoIB, STGT iSER, SCST iSCSI via IPoIB, SCST SRP, LIO iSCSI via IPoIB. The reason I chose dd/xdd for these tests is that I want to measure the performance of the communication protocols, and that I am assuming that this performance can be modeled by the following formula: (transfer time in s) = (transfer setup latency in s) + (transfer size in MB) / (bandwidth in MB/s). Measuring the time needed for transfers with varying block size allows to compute the constants in the above formula via linear regression. One difficulty I already encountered is that the performance of the Linux IPoIB implementation varies a lot under high load (http://bugzilla.kernel.org/show_bug.cgi?id=9883). Another issue I have to look further into is that dd and xdd report different results for very large block sizes (> 1 MB). Bart Van Assche. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/