From owner-freebsd-scsi Sun Feb 4 18: 9:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id E994037B491 for ; Sun, 4 Feb 2001 18:09:33 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f152AUc01543; Sun, 4 Feb 2001 18:10:30 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200102050210.f152AUc01543@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: Re: Tags and the mly driver In-reply-to: Your message of "Sun, 04 Feb 2001 12:41:49 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Feb 2001 18:10:30 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > According to camcontrol, SCSI disks attached via the mly driver are not > using tagged command queuing by default. > > I've been investigating why the performance of the a Mylex AccelRAID 352 > (mly driver) was about 30 to 40% slower than an older Mylex AccelRAID 250 > (mlx driver). mly uses the CAM layer, and mlx does not. Performance was > measured with postmark using 10,000 files, and 50,000 transactions. > > Anyhow, attempts to raise the number of tags via camcontrol via seems to > work (camcontrol tags da0 -N 4), however shortly after increasing it to > 16, the entire disk array hung. > > Are tags just unsupported on drivers that provide a virtualized SCSI > interface like the mly driver? Or are there driver and/or hardware > limitations that prevent them working? I'm not entirely sure what the problem is here; it was my impression that by returning PI_TAG_ABLE in hba_inquiry from XPT_PATH_INQ that tagged command queueing would automatically be enabled. As it stands, this is probably a vindication of my general preference not to make RAID volumes look like SCSI disks - they don't typically behave anything like them, and stupid things happen when you try. Inre: your other message; the "AM completion for illegal slot" message means that the controller returned a completion status indicator for a command ID that was not actually in use. I've recently fetched all my controllers back out of storage, so with any luck, I'll be able to post a followup to this in a little while with a better answer for you. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message