From owner-freebsd-questions Thu Jul 11 03:28:23 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA02420 for questions-outgoing; Thu, 11 Jul 1996 03:28:23 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA02415 for ; Thu, 11 Jul 1996 03:28:21 -0700 (PDT) Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA10945; Thu, 11 Jul 1996 05:25:32 -0500 Message-Id: <9607111025.AA10945@iworks.InterWorks.org> Date: Thu, 11 Jul 1996 05:25:32 -0500 From: "Daniel M. Eischen" To: freebsd-questions@freebsd.org, mark@ucsalf.ac.uk Subject: Re: Does Adaptec 7880 Ultra support simultaneous wide and narrow transfers? Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have a motherboard with a built in 7880 Ultra with a narrow and a wide connector > surface mounted. I have a Conner CFP4207S on the narrow channel with TERM/PWR enabled > and a Conner CFP4207W on the wide channel with TERM/PWR enabled. I wanted to move my > FreeBSD-2.1-stable filesystem from the narrow disk to the wide. I assumed that I could > simply copy all the data over with (narrow on sd0, wide on sd1; with 512k on board > data buffer): > > $ dd if=/dev/sd0c of=/dev/sd1c bs=512k > > However, this only yields data transfer rates in the 200K/s range. I've tried both > larger and smaller buffer sizes with no apparent increase. I'm beginning to wonder > if the 7870 chipset is performing these transfers simultaneously. I would expect > such a command to push both drives at full speed with the drive access lights on > solidly. However, the drive lights are alternating off/no for around 1 sec. periods. > Am I expecting the wrong thing here? > If I turn on WIDE negotiation for the W drive, the kernel enables 16bit transfers: When did you get your -stable system? There were some bug fixes that were incorporated into the aic7xxx driver in late June. Make sure you're running a -stable after that date. If you want to increase performance, add option "AHC_TAGENABLE" to your kernel configuration. If all your devices handle tagged queueing properly, then you can try adding "AHC_SCBPAGING_ENABLE" to your kernel configuration also. For devices on both internal narrow and wide channels, you should have termination set to Low Off / High On. Dan Eischen deischen@iworks.InterWorks.org