From owner-freebsd-scsi Thu Mar 28 15:37:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 238E837B41A for ; Thu, 28 Mar 2002 15:37:49 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g2SNbek24105; Thu, 28 Mar 2002 16:37:40 -0700 (MST) (envelope-from ken) Date: Thu, 28 Mar 2002 16:37:40 -0700 From: "Kenneth D. Merry" To: Lukas Ertl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ciss driver and tagged queuing Message-ID: <20020328163740.A24032@panzer.kdm.org> References: <20020328152644.A23074@panzer.kdm.org> <20020328232901.L214-100000@korben.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020328232901.L214-100000@korben.in.tern>; from l.ertl@univie.ac.at on Thu, Mar 28, 2002 at 11:35:01PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 28, 2002 at 23:35:01 +0100, Lukas Ertl wrote: > On Thu, 28 Mar 2002, Kenneth D. Merry wrote: > > > What RAID level are you using? There are significant differences (on the > > smart array controller at least) between the block read and write results. > > With the SCSI->IDE controller, oddly, the write results are faster than the > > read results. > > RAID5. I don't have a lot of experience with RAID, so I don't know if the > number of disks have an influence on the result (12 80GB IDE disks in the > SCSI/IDE array, 8 72GB disks in the Compaq array). That explains why the block read performance is faster than the write performance on the Smart Array controller. With RAID-5, you have to do parity calculation on writes, so they'll be somewhat slower, more so if the board doesn't have a hardware parity engine. That doesn't explain why writes are faster than reads on the other array. > > What does dmesg say about the card? From looking at the driver, it looks > > like the "max outstanding commands" value that is printed out on boot will > > tell us how many outstanding transactions the card claims to support. > > Ok: > > ciss1: port 0x3000-0x30ff mem > 0xf7e00000-0xf7efffff,0x > f7fc0000-0xf7ffffff irq 3 at device 4.0 on pci7 > ciss1: using 256 of 1024 available commands > ciss1: 1 logical drive configured > ciss1: firmware 1.76 > ciss1: 2 SCSI channels > ciss1: signature 'CISS' > ciss1: valence 1 > ciss1: supported I/O methods 0xe > ciss1: active I/O method 0x3 > ciss1: 4G page base 0x00000000 > ciss1: interrupt coalesce delay 1000us > ciss1: interrupt coalesce count 0 > ciss1: max outstanding commands 1024 > ciss1: bus types 0x2 > ciss1: server name '' > ciss1: heartbeat 0x20000022 > ciss1: 1 logical drive > ciss1: logical drive 0: RAID 5, 416768MB online Okay, it looks like you should be able to send at least 256 simultaneous commands. What does dmesg say about da1 (which I assume is the smart array device)? (might be faster to just send the full dmesg output) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message