From owner-freebsd-hardware@FreeBSD.ORG Sun Feb 6 23:54:04 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6AC01065670; Sun, 6 Feb 2011 23:54:04 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 637C18FC15; Sun, 6 Feb 2011 23:54:04 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p16Ns060002096 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 6 Feb 2011 18:54:01 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D4F3497.6050505@sentex.net> Date: Sun, 06 Feb 2011 18:53:59 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jack Vogel References: <1290533941.3173.50.camel@home-yahoo> <4CEC0548.1080801@sentex.net> <4D2C636B.5040003@sentex.net> <4D3C4795.40205@sentex.net> <4D42EA74.4090807@sentex.net> <1296590190.2326.6.camel@hitfishpass-lx.corp.yahoo.com> <1296591565.2326.7.camel@hitfishpass-lx.corp.yahoo.com> <1296597827.2326.12.camel@hitfishpass-lx.corp.yahoo.com> <4D48C973.7080503@sentex.net> <4D49A26B.5050803@sentex.net> <1296842996.2233.0.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: "freebsd-net@freebsd.org" , "freebsd-hardware@freebsd.org" , Sean Bruno , Jan Koum , Ivan Voras Subject: Re: em driver, 82574L chip, and possibly ASPM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Feb 2011 23:54:05 -0000 So far so good. I would often get a hang on the level zero dumps to my backup server Sunday AM, and it made it through! So a good sign, but not a definitive sign. I have a PCIe em card that has this chipset as well and was showing the same sort of problem in a customer's RELENG_7 box. I will see if I can get the customer to try the card in their box with the patch for RELENG_7 as it would show this issue at least once a day until I pulled the card for an older version ---Mike On 2/4/2011 1:12 PM, Jack Vogel wrote: > Was curious too, but being more patient than you :) > > Jack > > > On Fri, Feb 4, 2011 at 10:09 AM, Sean Bruno wrote: > >> Any more data on this problem or do we have to wait a while? >> >> Sean >> >> >> On Wed, 2011-02-02 at 10:28 -0800, Mike Tancsa wrote: >>> On 2/2/2011 12:37 PM, Jack Vogel wrote: >>>> So has everyone that wanted to get something testing been able to do >> so? >>> >>> I have been testing in the back and will deploy to my production box >>> this afternoon. As I am not able to reproduce it easily, it will be a >>> bit before I can say the issue is gone. Jan however, was able to >>> trigger it with greater ease ? >>> >>> ---Mike >>> >>>> >>>> Jack >>>> >>>> >>>> On Tue, Feb 1, 2011 at 7:03 PM, Mike Tancsa wrote: >>>> >>>>> On 2/1/2011 5:03 PM, Sean Bruno wrote: >>>>>> On Tue, 2011-02-01 at 13:43 -0800, Jack Vogel wrote: >>>>>>> To those who are going to test, here is the if_em.c, based on head, >>>>>>> with my >>>>>>> changes, I have to leave for the afternoon, and have not had a >> chance >>>>>>> to build >>>>>>> this, but it should work. I will check back in the later evening. >>>>>>> >>>>>>> Any blatant problems Sean, feel free to fix them :) >>>>>>> >>>>>>> Jack >>>>>>> >>>>>> >>>>>> >>>>>> I suspect that line 1490 should be: >>>>>> if (more_rx || (ifp->if_drv_flags & IFF_DRV_OACTIVE)) { >>>>>> >>>>> >>>>> >>>>> I have hacked up a RELENG_8 version which I think is correct including >>>>> the above change >>>>> >>>>> http://www.tancsa.com/if_em-8.c >>>>> >>>>> >>>>> >>>>> --- if_em.c.orig 2011-02-01 21:47:14.000000000 -0500 >>>>> +++ if_em.c 2011-02-01 21:47:19.000000000 -0500 >>>>> @@ -30,7 +30,7 @@ >>>>> POSSIBILITY OF SUCH DAMAGE. >>>>> >>>>> >>>>> >> ******************************************************************************/ >>>>> -/*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.21.2.20 2011/01/22 01:37:53 >>>>> jfv Exp $*/ >>>>> +/*$FreeBSD$*/ >>>>> >>>>> #ifdef HAVE_KERNEL_OPTION_HEADERS >>>>> #include "opt_device_polling.h" >>>>> @@ -93,7 +93,7 @@ >>>>> >> /********************************************************************* >>>>> * Driver version: >>>>> >> *********************************************************************/ >>>>> -char em_driver_version[] = "7.1.9"; >>>>> +char em_driver_version[] = "7.1.9-test"; >>>>> >>>>> >> /********************************************************************* >>>>> * PCI Device ID Table >>>>> @@ -927,11 +927,10 @@ >>>>> if (!adapter->link_active) >>>>> return; >>>>> >>>>> - /* Call cleanup if number of TX descriptors low */ >>>>> - if (txr->tx_avail <= EM_TX_CLEANUP_THRESHOLD) >>>>> - em_txeof(txr); >>>>> - >>>>> while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { >>>>> + /* First cleanup if TX descriptors low */ >>>>> + if (txr->tx_avail <= EM_TX_CLEANUP_THRESHOLD) >>>>> + em_txeof(txr); >>>>> if (txr->tx_avail < EM_MAX_SCATTER) { >>>>> ifp->if_drv_flags |= IFF_DRV_OACTIVE; >>>>> break; >>>>> @@ -1411,8 +1410,7 @@ >>>>> if (!drbr_empty(ifp, txr->br)) >>>>> em_mq_start_locked(ifp, txr, NULL); >>>>> #else >>>>> - if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) >>>>> - em_start_locked(ifp, txr); >>>>> + em_start_locked(ifp, txr); >>>>> #endif >>>>> EM_TX_UNLOCK(txr); >>>>> >>>>> @@ -1475,11 +1473,10 @@ >>>>> struct ifnet *ifp = adapter->ifp; >>>>> struct tx_ring *txr = adapter->tx_rings; >>>>> struct rx_ring *rxr = adapter->rx_rings; >>>>> - bool more; >>>>> - >>>>> >>>>> if (ifp->if_drv_flags & IFF_DRV_RUNNING) { >>>>> - more = em_rxeof(rxr, adapter->rx_process_limit, NULL); >>>>> + bool more_rx; >>>>> + more_rx = em_rxeof(rxr, adapter->rx_process_limit, >> NULL); >>>>> >>>>> EM_TX_LOCK(txr); >>>>> em_txeof(txr); >>>>> @@ -1487,12 +1484,10 @@ >>>>> if (!drbr_empty(ifp, txr->br)) >>>>> em_mq_start_locked(ifp, txr, NULL); >>>>> #else >>>>> - if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) >>>>> - em_start_locked(ifp, txr); >>>>> + em_start_locked(ifp, txr); >>>>> #endif >>>>> - em_txeof(txr); >>>>> EM_TX_UNLOCK(txr); >>>>> - if (more) { >>>>> + if (more_rx || (ifp->if_drv_flags & IFF_DRV_OACTIVE)) >> { >>>>> taskqueue_enqueue(adapter->tq, >> &adapter->que_task); >>>>> return; >>>>> } >>>>> @@ -1604,7 +1599,6 @@ >>>>> if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) >>>>> em_start_locked(ifp, txr); >>>>> #endif >>>>> - em_txeof(txr); >>>>> E1000_WRITE_REG(&adapter->hw, E1000_IMS, txr->ims); >>>>> EM_TX_UNLOCK(txr); >>>>> } >>>>> @@ -3730,17 +3724,17 @@ >>>>> txr->queue_status = EM_QUEUE_HUNG; >>>>> >>>>> /* >>>>> - * If we have enough room, clear IFF_DRV_OACTIVE >>>>> + * If we have a minimum free, clear IFF_DRV_OACTIVE >>>>> * to tell the stack that it is OK to send packets. >>>>> */ >>>>> - if (txr->tx_avail > EM_TX_CLEANUP_THRESHOLD) { >>>>> + if (txr->tx_avail > EM_MAX_SCATTER) >>>>> ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; >>>>> - /* Disable watchdog if all clean */ >>>>> - if (txr->tx_avail == adapter->num_tx_desc) { >>>>> - txr->queue_status = EM_QUEUE_IDLE; >>>>> - return (FALSE); >>>>> - } >>>>> - } >>>>> + >>>>> + /* Disable watchdog if all clean */ >>>>> + if (txr->tx_avail == adapter->num_tx_desc) { >>>>> + txr->queue_status = EM_QUEUE_IDLE; >>>>> + return (FALSE); >>>>> + } >>>>> >>>>> return (TRUE); >>>>> } >>>>> @@ -5064,8 +5058,8 @@ >>>>> char namebuf[QUEUE_NAME_LEN]; >>>>> >>>>> /* Driver Statistics */ >>>>> - SYSCTL_ADD_UINT(ctx, child, OID_AUTO, "link_irq", >>>>> - CTLFLAG_RD, &adapter->link_irq, 0, >>>>> + SYSCTL_ADD_UINT(ctx, child, OID_AUTO, "link_irq", >>>>> + CTLFLAG_RD, &adapter->link_irq,0, >>>>> "Link MSIX IRQ Handled"); >>>>> SYSCTL_ADD_ULONG(ctx, child, OID_AUTO, "mbuf_alloc_fail", >>>>> CTLFLAG_RD, &adapter->mbuf_alloc_failed, >>>>> @@ -5108,11 +5102,13 @@ >>>>> queue_list = SYSCTL_CHILDREN(queue_node); >>>>> >>>>> SYSCTL_ADD_PROC(ctx, queue_list, OID_AUTO, "txd_head", >>>>> - CTLFLAG_RD, adapter, >> E1000_TDH(txr->me), >>>>> + CTLFLAG_RD, adapter, >>>>> + E1000_TDH(txr->me), >>>>> em_sysctl_reg_handler, "IU", >>>>> "Transmit Descriptor Head"); >>>>> SYSCTL_ADD_PROC(ctx, queue_list, OID_AUTO, "txd_tail", >>>>> - CTLFLAG_RD, adapter, >> E1000_TDT(txr->me), >>>>> + CTLFLAG_RD, adapter, >>>>> + E1000_TDT(txr->me), >>>>> em_sysctl_reg_handler, "IU", >>>>> "Transmit Descriptor Tail"); >>>>> SYSCTL_ADD_ULONG(ctx, queue_list, OID_AUTO, "tx_irq", >>>>> @@ -5123,11 +5119,13 @@ >>>>> "Queue No Descriptor Available"); >>>>> >>>>> SYSCTL_ADD_PROC(ctx, queue_list, OID_AUTO, "rxd_head", >>>>> - CTLFLAG_RD, adapter, >> E1000_RDH(rxr->me), >>>>> + CTLFLAG_RD, adapter, >>>>> + E1000_RDH(rxr->me), >>>>> em_sysctl_reg_handler, "IU", >>>>> "Receive Descriptor Head"); >>>>> SYSCTL_ADD_PROC(ctx, queue_list, OID_AUTO, "rxd_tail", >>>>> - CTLFLAG_RD, adapter, >> E1000_RDT(rxr->me), >>>>> + CTLFLAG_RD, adapter, >>>>> + E1000_RDT(rxr->me), >>>>> em_sysctl_reg_handler, "IU", >>>>> "Receive Descriptor Tail"); >>>>> SYSCTL_ADD_ULONG(ctx, queue_list, OID_AUTO, "rx_irq", >>>>> @@ -5141,19 +5139,19 @@ >>>>> CTLFLAG_RD, NULL, "Statistics"); >>>>> stat_list = SYSCTL_CHILDREN(stat_node); >>>>> >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "excess_coll", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "excess_coll", >>>>> CTLFLAG_RD, &stats->ecol, >>>>> "Excessive collisions"); >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "single_coll", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "single_coll", >>>>> CTLFLAG_RD, &stats->scc, >>>>> "Single collisions"); >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "multiple_coll", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "multiple_coll", >>>>> CTLFLAG_RD, &stats->mcc, >>>>> "Multiple collisions"); >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "late_coll", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "late_coll", >>>>> CTLFLAG_RD, &stats->latecol, >>>>> "Late collisions"); >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "collision_count", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "collision_count", >>>>> CTLFLAG_RD, &stats->colc, >>>>> "Collision Count"); >>>>> SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "symbol_errors", >>>>> @@ -5240,12 +5238,12 @@ >>>>> SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, >> "rx_frames_1024_1522", >>>>> CTLFLAG_RD, &adapter->stats.prc1522, >>>>> "1023-1522 byte frames received"); >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "good_octets_recvd", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "good_octets_recvd", >>>>> CTLFLAG_RD, &adapter->stats.gorc, >>>>> "Good Octets Received"); >>>>> >>>>> /* Packet Transmission Stats */ >>>>> - SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "good_octets_txd", >>>>> + SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "good_octets_txd", >>>>> CTLFLAG_RD, &adapter->stats.gotc, >>>>> "Good Octets Transmitted"); >>>>> SYSCTL_ADD_QUAD(ctx, stat_list, OID_AUTO, "total_pkts_txd", >>>>> >>>>> -- >>>>> ------------------- >>>>> Mike Tancsa, tel +1 519 651 3400 >>>>> Sentex Communications, mike@sentex.net >>>>> Providing Internet services since 1994 www.sentex.net >>>>> Cambridge, Ontario Canada http://www.tancsa.com/ >>>>> >>>> >>> >>> >>> -- >>> ------------------- >>> Mike Tancsa, tel +1 519 651 3400 >>> Sentex Communications, mike@sentex.net >>> Providing Internet services since 1994 www.sentex.net >>> Cambridge, Ontario Canada http://www.tancsa.com/ >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> >> > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 7 18:55:47 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E9A8106564A for ; Mon, 7 Feb 2011 18:55:47 +0000 (UTC) (envelope-from weiler@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id 708018FC15 for ; Mon, 7 Feb 2011 18:55:47 +0000 (UTC) Received: from wraith.cse.ucsc.edu (wraith.cse.ucsc.edu [128.114.56.35]) by mail-01.cse.ucsc.edu (Postfix) with ESMTPSA id A11221009BA0 for ; Mon, 7 Feb 2011 10:40:03 -0800 (PST) Message-ID: <4D503C83.70005@soe.ucsc.edu> Date: Mon, 07 Feb 2011 10:40:03 -0800 From: Erich Weiler User-Agent: Thunderbird 2.0.0.24 (X11/20100318) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Dell Perc H800 controller errors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2011 18:55:47 -0000 Hi All, I've scoured around and can't seem to find others with this exact issue, so I'm hoping someone here will be able to shed light on this... We have a FreeBSD server running: FreeBSD 8.2-PRERELEASE (GENERIC) #0: Thu Dec 16 14:59:46 PST 2010 It's a Dell R610. It has two MD1200 disk arrays on it, SAS chained together. The controller that manages them is a Perc H800, with the latest firmware available. I have the disks exported JBOD from the controller. And, the disks are roped into a ZFS filesystem, which is exported via NFS to the local net. Everything works well most of the time, but every once in a while (like once every few days), the filesystem completely hangs and we see these errors on the console: mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 61793 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 61823 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 61853 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 61923 SECONDS (this is after the filesystem has been hung for a day) etc... When I start poking around with mfiutil, it shows everything is OK, the disks are all OK, the volumes are good, the event logs show no errors. The "Patrol" feature is disabled. The battery is fine. After running a few of these "mfiutil show drives" and "mfiutil show [volumes|config]" commands, the lockup magically frees itself. But, I don't want them to happen in the first place, and I certainly don't want to have to manually run a "mfiutil show disks" or whatever to unlock it every time. Has anyone seen this before? I've actually tried another H800 controller we had on the shelf as well, just to rule out a hardware problem with the first one, but we see the same behavior on both controllers. "zpool status" also shows the disks as all OK, and a "zpool scrub" turns up no problems. Any insight much appreciated!! -erich From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 8 22:16:06 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C801106564A for ; Tue, 8 Feb 2011 22:16:06 +0000 (UTC) (envelope-from jose.amengual@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24EE18FC16 for ; Tue, 8 Feb 2011 22:16:05 +0000 (UTC) Received: by fxm16 with SMTP id 16so6897046fxm.13 for ; Tue, 08 Feb 2011 14:16:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=medwOdI/lvBq6oTuWRyVa8xK6hFjjVt7gbp9ouODkdw=; b=QqW/+aPO140Y8ThEEEddJypTtiDoQtEShKMY/NZt31FzQRM1dSzCKM4lJ8VFrhstYF FGZVrjL+uHZxhgLAfqQvHe6AIyJqugPhukvcfq6dRQ7nRW9fV/gi1FRvjsFVSFzsubXH OxizGSCd+sJzaTJ1+rMUkSRSDEM6f3+NlfOn8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=LHkBGv6jWxAlvGiP9I8jk2NBdrBp5PK2PktHZLS7paH4R7Rx6TiJhN12a9FI6D9OaG yxrvInGJi52UrAg4ikTzBC3binbpLVS1GomsxTgWBr0YwNgILMnPnltk1cCW/3+IZIgG htIp6/4a7lXDJlj0be6d+eHpuHibnZuYAl1Ys= Received: by 10.223.54.132 with SMTP id q4mr8344308fag.117.1297201805633; Tue, 08 Feb 2011 13:50:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.74.141 with HTTP; Tue, 8 Feb 2011 13:49:45 -0800 (PST) From: Jose Amengual Date: Tue, 8 Feb 2011 13:49:45 -0800 Message-ID: To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Addonics SIS3124 Controller and T X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2011 22:16:06 -0000 Hi guys. I just recently bought this controller : http://www.addonics.com/products/host_controller/adsa3gpx8-4e.asp Plus : http://www.addonics.com/products/raid_tower/raid_rack.asp ( the one with 4esata connectors in the back) so I have a 8.1-RELEASE running and the controlled connected and the siis driver loaded plus 10 HDs installed on the raidrack each 5 is connected to a 5x1 port mutiplier and then to a esata. so here is the issue : 1.- I can see just only from ada0 to ada6 I don't see any other HDs. 2.- Performance is just 131 MBs per second as report from diskinfo -t superstorage1# diskinfo -t /dev/ada0 /dev/ada0 512 # sectorsize 1000204886016 # mediasize in bytes (932G) 1953525168 # mediasize in sectors 0 # stripesize 0 # stripeoffset 1938021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. WD-WCATR5253676 # Disk ident. Seek times: Full stroke: 250 iter in 5.055337 sec = 20.221 msec Half stroke: 250 iter in 3.685852 sec = 14.743 msec Quarter stroke: 500 iter in 5.924198 sec = 11.848 msec Short forward: 400 iter in 2.157650 sec = 5.394 msec Short backward: 400 iter in 1.785152 sec = 4.463 msec Seq outer: 2048 iter in 0.292870 sec = 0.143 msec Seq inner: 2048 iter in 0.232126 sec = 0.113 msec Transfer rates: outside: 102400 kbytes in 0.771598 sec = 132712 kbytes/sec middle: 102400 kbytes in 0.925421 sec = 110652 kbytes/sec inside: 102400 kbytes in 1.652984 sec = 61949 kbytes/sec it should be more ? 3.- I have two different system with same controller one is a dell 2850 and the other one is a supermicro server in both I can see only 7 HDs. Could be a problem with the driver ? So my idea was that to use this with ZFS and AOE so I can have a SAN for my servers but I need to get the best performance possible. I'm willing to buy another controller if is necessary, any recommendations ? ( no more than 700 US ) some additional info : siis0@pci0:9:0:0: class=0x018000 card=0x31241095 chip=0x31241095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'PCI-X to Serial ATA Controller (SiI 3124)' class = mass storage aac0@pci0:7:0:0: class=0x010400 card=0x02ca15d9 chip=0x02859005 rev=0x09 hdr=0x00 vendor = 'Adaptec Inc' device = 'PCIX133 32/64bit (Adaptec 2410SA SATA RAID)' class = mass storage subclass = RAID Thanks. From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 9 02:57:56 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9FFD106566B for ; Wed, 9 Feb 2011 02:57:56 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from imr-ma02.mx.aol.com (imr-ma02.mx.aol.com [64.12.206.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8A8D08FC13 for ; Wed, 9 Feb 2011 02:57:56 +0000 (UTC) Received: from imo-da03.mx.aol.com (imo-da03.mx.aol.com [205.188.169.201]) by imr-ma02.mx.aol.com (8.14.1/8.14.1) with ESMTP id p192ljIT004068 for ; Tue, 8 Feb 2011 21:47:45 -0500 Received: from dieterbsd@engineer.com by imo-da03.mx.aol.com (mail_out_v42.9.) id n.bf9.87c02caf (37532) for ; Tue, 8 Feb 2011 21:47:41 -0500 (EST) Received: from smtprly-db01.mx.aol.com (smtprly-db01.mx.aol.com [205.188.249.152]) by cia-mb01.mx.aol.com (v129.8) with ESMTP id MAILCIAMB015-5bc84d5200438b; Tue, 08 Feb 2011 21:47:41 -0500 Received: from web-mmc-m02 (web-mmc-m02.sim.aol.com [64.12.224.135]) by smtprly-db01.mx.aol.com (v129.8) with ESMTP id MAILSMTPRLYDB017-5bc84d5200438b; Tue, 08 Feb 2011 21:47:31 -0500 To: freebsd-hardware@freebsd.org Content-Transfer-Encoding: quoted-printable Date: Tue, 08 Feb 2011 21:47:31 -0500 X-MB-Message-Source: WebUI X-AOL-IP: 67.206.161.198 X-MB-Message-Type: User MIME-Version: 1.0 From: dieterbsd@engineer.com Content-Type: text/plain; charset="us-ascii" X-Mailer: Mail.com Webmail 33189-STANDARD Received: from 67.206.161.198 by web-mmc-m02.sysops.aol.com (64.12.224.135) with HTTP (WebMailUI); Tue, 08 Feb 2011 21:47:31 -0500 Message-Id: <8CD961AD4EE6A77-1804-38AC@web-mmc-m02.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: dieterbsd@engineer.com Subject: Re: Addonics SIS3124 Controller and T X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2011 02:57:56 -0000 Jose Amengual writes: > 1.- I can see just only from ada0 to ada6 I don't see any other HDs. Are both of the JMB393s configured as individual drives port multiplier mode? (as opposed to some hardware raid mode) I assume you've already checked the cables. > 2.- Performance is just 131 MBs per second as report from diskinfo -t This is for an individual drive, correct? How fast do you expect it to be? Have you tried connecting individual drives to the 3124 controller and tested the performance that way? >From what you've written, the bottleneck could be the controller, the port multiplier, or the drive itself. 131 MB/s sounds about right for a single drive, unless it is some super high performance drive or you are reading from the drive's RAM rather than from the platters. I can get 253 MB/s reading from a drive's RAM. Useful for seeing what controllers, port multipliers and such can do without the limits of the platter density. (the platter density goes up as new generations of drives come out) I'd be interested in knowing what the 3124 controller and the JMB393 PM can do. From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 9 09:41:50 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54EC6106567A for ; Wed, 9 Feb 2011 09:41:50 +0000 (UTC) (envelope-from jose.amengual@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 248A68FC14 for ; Wed, 9 Feb 2011 09:41:49 +0000 (UTC) Received: by pxi1 with SMTP id 1so1549819pxi.13 for ; Wed, 09 Feb 2011 01:41:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=meHhiR8g00QTWpGZ/+m7vnlLRNdgbXC+zap+Nt6LPpQ=; b=ntRTv6TZpQKWoFb4ZLSWkN7kezj3eFhj49i/U75YR+swAqoBr7CD+JMLedNSEewyoX 74CYT24/xaHFd1uXgQo9k5WfXkODyIxpcAH5AbYI8HKEqSJD3BhGoLnu+SaUc1TEY5fb itOF+jZYdKwBS2tFRZjlXK57FzxtAaSmLS4LQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=DSjE/Xvcjg3W7sfvwM2FGm7gKFqiadT+Wx7r3hD9vOPOV83mmGv7WIsPc/v/LnJnhC 22DUV0mbmPK/FU9S04lmFC2xwCWwGrjtwVA8g0++lgQQWYQ3MYDdOM30Y8u6PLz2+6Gs Ixct80GgVrX9NLoXpWy/zOVUZ2wd3FgjebUdc= Received: by 10.142.187.12 with SMTP id k12mr2372042wff.46.1297244509299; Wed, 09 Feb 2011 01:41:49 -0800 (PST) Received: from [192.168.18.100] (S0106001310f0bb09.vc.shawcable.net [24.84.209.121]) by mx.google.com with ESMTPS id w22sm158359wfd.7.2011.02.09.01.41.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Feb 2011 01:41:47 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Jose Amengual In-Reply-To: <8CD961AD4EE6A77-1804-38AC@web-mmc-m02.sysops.aol.com> Date: Wed, 9 Feb 2011 01:41:46 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <9B050F94-41D4-425B-9B06-8D1D85CF9B0E@gmail.com> References: <8CD961AD4EE6A77-1804-38AC@web-mmc-m02.sysops.aol.com> To: dieterbsd@engineer.com X-Mailer: Apple Mail (2.1082) Cc: freebsd-hardware@freebsd.org Subject: Re: Addonics SIS3124 Controller and T X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2011 09:41:50 -0000 On 2011-02-08, at 6:47 PM, dieterbsd@engineer.com wrote: > Jose Amengual writes: >> 1.- I can see just only from ada0 to ada6 I don't see any other HDs. >=20 > Are both of the JMB393s configured as individual drives port = multiplier > mode? (as opposed to some hardware raid mode) I assume you've already > checked the cables. Strangely enough just switching drives now I can see all ten, weird but = is working now. I'm confused why you are referring to a JMB393s if my card has a = siis3124 chip....or are you referring o the PMs? >=20 >> 2.- Performance is just 131 MBs per second as report from diskinfo -t >=20 > This is for an individual drive, correct? =20 > How fast do you expect it to > be? This was for an individual drive. I was expecting more but it looks like I was wrong with my assumptions.=20= >=20 > Have you tried connecting individual drives to the 3124 controller > and tested the performance that way? I didn't try this, I will do that. >=20 >> =46rom what you've written, the bottleneck could be the controller, = the > port multiplier, or the drive itself. 131 MB/s sounds about right > for a single drive, unless it is some super high performance drive > or you are reading from the drive's RAM rather than from the platters. > I can get 253 MB/s reading from a drive's RAM. Useful for seeing what > controllers, port multipliers and such can do without the limits of > the platter density. (the platter density goes up as new generations > of drives come out) I'd be interested in knowing what the 3124 > controller and the JMB393 PM can do. >=20 >=20 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to = "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 10 00:36:25 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 222D2106566C for ; Thu, 10 Feb 2011 00:36:25 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from imr-da06.mx.aol.com (imr-da06.mx.aol.com [205.188.169.203]) by mx1.freebsd.org (Postfix) with ESMTP id D3EE98FC1B for ; Thu, 10 Feb 2011 00:36:24 +0000 (UTC) Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-da06.mx.aol.com (8.14.1/8.14.1) with ESMTP id p1A0aFO0011030 for ; Wed, 9 Feb 2011 19:36:15 -0500 Received: from dieterbsd@engineer.com by imo-ma02.mx.aol.com (mail_out_v42.9.) id n.fce.bf7f48f (45494) for ; Wed, 9 Feb 2011 19:36:11 -0500 (EST) Received: from smtprly-dc03.mx.aol.com (smtprly-dc03.mx.aol.com [205.188.170.3]) by cia-mc08.mx.aol.com (v129.7) with ESMTP id MAILCIAMC081-d3a34d5332f8236; Wed, 09 Feb 2011 19:36:11 -0500 Received: from web-mmc-d01 (web-mmc-d01.sim.aol.com [205.188.103.67]) by smtprly-dc03.mx.aol.com (v129.8) with ESMTP id MAILSMTPRLYDC033-d3a34d5332f8236; Wed, 09 Feb 2011 19:36:08 -0500 To: freebsd-hardware@freebsd.org Content-Transfer-Encoding: quoted-printable Date: Wed, 09 Feb 2011 19:36:08 -0500 X-MB-Message-Source: WebUI X-AOL-IP: 67.206.161.238 X-MB-Message-Type: User MIME-Version: 1.0 From: dieterbsd@engineer.com Content-Type: text/plain; charset="us-ascii" X-Mailer: Mail.com Webmail 33222-STANDARD Received: from 67.206.161.238 by web-mmc-d01.sysops.aol.com (205.188.103.67) with HTTP (WebMailUI); Wed, 09 Feb 2011 19:36:08 -0500 Message-Id: <8CD96D1A47516BC-11A8-283B@web-mmc-d01.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: dieterbsd@engineer.com Subject: Re: Addonics SIS3124 Controller and T X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2011 00:36:25 -0000 Jose Amengual writes: > Strangely enough just switching drives now I can see all ten, weird > but is working now. Perhaps there was a loose conection or something. > I'm confused why you are referring to a JMB393s if my card has a > siis3124 chip....or are you referring o the PMs? If I'm reading http://www.addonics.com/products/raid_tower/raid_rack.asp correctly, it comes with 4 SATA Port Multipliers based on the JMB393 chip. Do you get something like PM Product ID: 37261095 in dmesg? I just got a PM based on the Sil3726. So far so good. I've been running some simple speed tests on it and various controllers. If you and your machine have a few minutes to spare, I'd love to see similar numbers for the siis3124 controller and the JMB393 PM. First I ran one disk at a time: nforce4-ultra controller chipset ata(4) ad4 249.404517 MB/s ad6 250.143419 MB/s ad8 239.214086 MB/s ad10 249.628334 MB/s SiI 3132 PCIe-x1 siis(4) ada0 127.737664 MB/s ada1 110.236024 MB/s ada2 110.210423 MB/s JMB363 PCIe-x1 ahci(4) ada3 131.443644 MB/s Sil3726 Port Multiplier ada4 130.895997 MB/s ada5 130.259701 MB/s ada6 132.400908 MB/s ada7 114.306864 MB/s ada8 130.986963 MB/s I need to rerun the tests (machine is busy right now) and see if the results are consistant. Some of the differences may be due to the different make & model drives. 2 disks at once - port multiplier drives ada4, ada5 48.034694 MB/s and 48.034701 MB/s Total: 96.069395 MB/s 2 disks at once - same card (jmb363) ada3 direct connection, ada5 via PM 86.059754 MB/s and 85.664682 MB/s Total: 171.724436 MB/s 3 disks at once - port multiplier drives ada4, ada5, ada6 31.728884 MB/s, 31.727878 MB/s, and 31.727715 MB/s Total: 95.184477 MB/s 4 disks at once - port multiplier drives ada4, ada5, ada6, ada8 23.657665 MB/s 23.657404 MB/s 23.657416 MB/s 23.657436 MB/s Total: 94.629921 MB/s 5 port multiplier disks at once 18.660235 MB/s 18.659920 MB/s 18.659928 MB/s 18.659925 MB/s 18.665027 MB/s 5 port multiplier disks at once plus the other port of the jmb363 105.348778 MB/s 17.821848 MB/s 17.821214 MB/s 17.821113 MB/s 17.821120 MB/s 17.821458 MB/s PM total (5 drives): 89.106753 MB/s Card total (6 drives): 194.455531 MB/s Neither the 3132 nor the 363 controllers can max out the PCIe-x1 link (250 MB/s each direction). Previous testing indicates that both achive a higher total with one disk reading and the other writing. (not sure why) Port multipliers may be the same, I haven't had time to test that case yet. I also want to test the PM with the 3132. Silicon Image SATA controllers are not the fastest. The JMB363 is faster than the 3132, so I wonder if the JMB393 port multiplier is faster than the Sil3726? I've read that the 3124 controller is fast, the question is how fast? Below is the small C program I used. It just reads a small amount of data over and over again from the drive's RAM cache. This avoids limitations of data density on the platters, rpm, seek time, etc. /* * read_disk_cache_speed.c * * Read data from a disk's RAM cache buffer. * Useful for testing the speed of controllers and port multipliers * without the limitation of how fast the disk can read data from the * platters. Note that the drive's electronics could still be the * limiting factor. * * Syntax: read_disk_cache_speed device readsize iterations * FreeBSD: * read_disk_cache_speed /dev/ada0 65536 10000 * NetBSD: * read_disk_cache_speed /dev/rwd0c 65536 10000 * * Original program was by: * Manuel Bouyer * NetBSD: 26 ans d'experience feront toujours la difference * Updated by: * Dieter * Added command line argument for buffer/read size. * (originally hard coded at 64 KiB) * Read data into drive's RAM buffer before beginning timing. * */ #include #include #include #include #include int main(int argc, char **argv) { int fd; /* file descriptor */ int i; /* loop counter */ struct timeval tv0, tv1; long t; /* elapsed time */ char *buffer; long buffer_size; if ( argc !=3D 4 ) { fprintf(stderr, "Syntax: %s device readsize iterations\n", argv[0]); fprintf(stderr, "Example: %s /dev/ada4 65536 10000\n", argv[0]); exit(1); } buffer_size =3D atoi(argv[2]); buffer =3D malloc(buffer_size); if ( buffer =3D=3D NULL ) { perror("malloc failed"); exit(1); } fd =3D open(argv[1], O_RDONLY, 0); if (fd < 0) { perror("open failed"); exit(1); } /* Get the data from the platter into the drive's RAM buffer * before we start timing. */ if (read(fd, (void *)buffer, buffer_size) !=3D buffer_size) { perror("read failed"); exit(1); } if (lseek(fd, 0, SEEK_SET) < 0) { perror("lseek failed"); exit(1); } if (gettimeofday(&tv0, NULL) < 0) { perror("gettimeofday failed"); exit(1); } for (i =3D 0; i < atoi(argv[3]); i++) { if (read(fd, (void *)buffer, buffer_size) !=3D buffer_size) { perror("read failed"); exit(1); } if (lseek(fd, 0, SEEK_SET) < 0) { perror("lseek failed"); exit(1); } } if (gettimeofday(&tv1, NULL) < 0) { perror("gettimeofday failed"); exit(1); } t =3D (tv1.tv_sec - tv0.tv_sec) * 1000000; t =3D t + tv1.tv_usec - tv0.tv_usec; printf("%ld us, %f MB/s\n", t, ((double)buffer_size * (double)i / 1000000) / ((double)t / 1000000)); exit(0); } Total: 93.305028 MB/s From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 10 07:18:25 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF67E1065679 for ; Thu, 10 Feb 2011 07:18:25 +0000 (UTC) (envelope-from jose.amengual@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7EA1D8FC1E for ; Thu, 10 Feb 2011 07:18:25 +0000 (UTC) Received: by pvc22 with SMTP id 22so196947pvc.13 for ; Wed, 09 Feb 2011 23:18:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=ZEqCEbOJxraEk4qV8Uhx+L5xNmB87x6iQo2B1EYsGWc=; b=G5G4BCvaajReKOQ8SCrn0JudSgwJnHHHN4/V33pPQpyI02iylFH4wJ39FU5QdSrmPt 0bQaH5N1exx9mp7YptmPgxVyz+p1LBjNbqsREMIgly0GG3cwLXMKZcVCVYLwv1dXmAP4 vZlbPf1Uuxb7ArOvd2rBtnmGgTRYT74ehhxVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=mwP1LnV5qocyXSNIyBT/XyyInwK1szsKoBk1n9GXFArGNdILWegJONKB5iJngGNhQ6 T2TQrWHdB37VKmVm2yuhKBxqBoLRZykuxpbPa9hMni0fvfT4O305rOKVolalWrBiSfPI U22/G+ecakwKySfhDX8TF+JntlVDEAPlC3A+w= Received: by 10.142.131.20 with SMTP id e20mr19489044wfd.309.1297322304895; Wed, 09 Feb 2011 23:18:24 -0800 (PST) Received: from [192.168.18.100] (S0106001310f0bb09.vc.shawcable.net [24.84.209.121]) by mx.google.com with ESMTPS id x18sm1492427wfa.23.2011.02.09.23.18.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Feb 2011 23:18:22 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Jose Amengual In-Reply-To: <8CD96D1A47516BC-11A8-283B@web-mmc-d01.sysops.aol.com> Date: Wed, 9 Feb 2011 23:18:19 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <2041CDFF-99EA-4D58-BC17-AF847A17ABF6@gmail.com> References: <8CD96D1A47516BC-11A8-283B@web-mmc-d01.sysops.aol.com> To: dieterbsd@engineer.com X-Mailer: Apple Mail (2.1082) Cc: freebsd-hardware@freebsd.org Subject: Re: Addonics SIS3124 Controller and T X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2011 07:18:25 -0000 On 2011-02-09, at 4:36 PM, dieterbsd@engineer.com wrote: > Jose Amengual writes: >> Strangely enough just switching drives now I can see all ten, weird >> but is working now. >=20 > Perhaps there was a loose connection or something. I think so=20 >=20 >> I'm confused why you are referring to a JMB393s if my card has a >> siis3124 chip....or are you referring o the PMs? >=20 > If I'm reading > http://www.addonics.com/products/raid_tower/raid_rack.asp > correctly, it comes with 4 SATA Port Multipliers based on > the JMB393 chip. I see.... >=20 > Do you get something like >=20 > PM Product ID: 37261095 I will check >=20 > in dmesg? I just got a PM based on the Sil3726. So far so good. > I've been running some simple speed tests on it and various > controllers. If you and your machine have a few minutes to spare, > I'd love to see similar numbers for the siis3124 controller and the > JMB393 PM. >=20 > First I ran one disk at a time: >=20 > nforce4-ultra controller chipset ata(4) > ad4 249.404517 MB/s > ad6 250.143419 MB/s > ad8 239.214086 MB/s > ad10 249.628334 MB/s >=20 > SiI 3132 PCIe-x1 siis(4) > ada0 127.737664 MB/s > ada1 110.236024 MB/s > ada2 110.210423 MB/s >=20 > JMB363 PCIe-x1 ahci(4) > ada3 131.443644 MB/s > Sil3726 Port Multiplier > ada4 130.895997 MB/s > ada5 130.259701 MB/s > ada6 132.400908 MB/s > ada7 114.306864 MB/s > ada8 130.986963 MB/s >=20 > I need to rerun the tests (machine is busy right now) and see if the > results are consistant. Some of the differences may be due to the > different make & model drives. >=20 > 2 disks at once - port multiplier drives ada4, ada5 > 48.034694 MB/s and 48.034701 MB/s > Total: 96.069395 MB/s >=20 > 2 disks at once - same card (jmb363) ada3 direct connection, ada5 via = PM > 86.059754 MB/s and 85.664682 MB/s > Total: 171.724436 MB/s >=20 > 3 disks at once - port multiplier drives ada4, ada5, ada6 > 31.728884 MB/s, 31.727878 MB/s, and 31.727715 MB/s > Total: 95.184477 MB/s >=20 > 4 disks at once - port multiplier drives ada4, ada5, ada6, ada8 > 23.657665 MB/s 23.657404 MB/s 23.657416 MB/s 23.657436 MB/s > Total: 94.629921 MB/s >=20 > 5 port multiplier disks at once > 18.660235 MB/s 18.659920 MB/s 18.659928 MB/s 18.659925 MB/s > 18.665027 MB/s > 5 port multiplier disks at once plus the other port of the jmb363 > 105.348778 MB/s 17.821848 MB/s 17.821214 MB/s 17.821113 MB/s > 17.821120 MB/s 17.821458 MB/s > PM total (5 drives): 89.106753 MB/s > Card total (6 drives): 194.455531 MB/s >=20 > Neither the 3132 nor the 363 controllers can max out the PCIe-x1 link > (250 MB/s each direction). Previous testing indicates that both > achive a higher total with one disk reading and the other writing. > (not sure why) Port multipliers may be the same, I haven't had time > to test that case yet. I also want to test the PM with the 3132. >=20 > Silicon Image SATA controllers are not the fastest. The JMB363 is > faster than the 3132, so I wonder if the JMB393 port multiplier is > faster than the Sil3726? I've read that the 3124 controller is > fast, the question is how fast? >=20 > Below is the small C program I used. It just reads a small amount > of data over and over again from the drive's RAM cache. This avoids > limitations of data density on the platters, rpm, seek time, etc. >=20 >=20 I check the raid controler and it doesn't have anything to enable any = level of caching but I have a Supermicro sata controller with cache = memory and and Intel chip that I will use for some testings. > /* > * read_disk_cache_speed.c > * > * Read data from a disk's RAM cache buffer. > * Useful for testing the speed of controllers and port multipliers > * without the limitation of how fast the disk can read data from the > * platters. Note that the drive's electronics could still be the > * limiting factor. > * > * Syntax: read_disk_cache_speed device readsize iterations > * FreeBSD: > * read_disk_cache_speed /dev/ada0 65536 10000 > * NetBSD: > * read_disk_cache_speed /dev/rwd0c 65536 10000 > * > * Original program was by: > * Manuel Bouyer > * NetBSD: 26 ans d'experience feront toujours la difference > * Updated by: > * Dieter > * Added command line argument for buffer/read size. > * (originally hard coded at 64 KiB) > * Read data into drive's RAM buffer before beginning timing. > * > */ >=20 > #include > #include > #include > #include > #include >=20 > int > main(int argc, char **argv) > { > int fd; /* file descriptor */ > int i; /* loop counter */ > struct timeval tv0, tv1; > long t; /* elapsed time */ > char *buffer; > long buffer_size; >=20 > if ( argc !=3D 4 ) > { > fprintf(stderr, "Syntax: %s device readsize iterations\n", > argv[0]); > fprintf(stderr, "Example: %s /dev/ada4 65536 10000\n", argv[0]); > exit(1); > } >=20 > buffer_size =3D atoi(argv[2]); > buffer =3D malloc(buffer_size); > if ( buffer =3D=3D NULL ) > { > perror("malloc failed"); > exit(1); > } >=20 > fd =3D open(argv[1], O_RDONLY, 0); > if (fd < 0) > { > perror("open failed"); > exit(1); > } > /* Get the data from the platter into the drive's RAM buffer > * before we start timing. > */ > if (read(fd, (void *)buffer, buffer_size) !=3D buffer_size) > { > perror("read failed"); > exit(1); > } > if (lseek(fd, 0, SEEK_SET) < 0) > { > perror("lseek failed"); > exit(1); > } >=20 > if (gettimeofday(&tv0, NULL) < 0) > { > perror("gettimeofday failed"); > exit(1); > } > for (i =3D 0; i < atoi(argv[3]); i++) > { > if (read(fd, (void *)buffer, buffer_size) !=3D buffer_size) > { > perror("read failed"); > exit(1); > } > if (lseek(fd, 0, SEEK_SET) < 0) > { > perror("lseek failed"); > exit(1); > } > } > if (gettimeofday(&tv1, NULL) < 0) > { > perror("gettimeofday failed"); > exit(1); > } > t =3D (tv1.tv_sec - tv0.tv_sec) * 1000000; > t =3D t + tv1.tv_usec - tv0.tv_usec; > printf("%ld us, %f MB/s\n", t, > ((double)buffer_size * (double)i / 1000000) / ((double)t / = 1000000)); > exit(0); > } I will use your program to test my hds and I will let you know. >=20 > Total: 93.305028 MB/s >=20 >=20 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to = "freebsd-hardware-unsubscribe@freebsd.org"