From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 16 05:32:50 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A6AC106564A; Mon, 16 Jan 2012 05:32:50 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog112.obsmtp.com (na3sys009aog112.obsmtp.com [74.125.149.207]) by mx1.freebsd.org (Postfix) with ESMTP id BA7168FC0A; Mon, 16 Jan 2012 05:32:49 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob112.postini.com ([74.125.148.12]) with SMTP ID DSNKTxO2gfk0odMSaXVBtjHJnuG38peBqoK4@postini.com; Sun, 15 Jan 2012 21:32:49 PST Received: from PALHUB01.lsi.com (128.94.213.114) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.137.0; Mon, 16 Jan 2012 00:25:57 -0500 Received: from inbexch01.lsi.com (135.36.98.37) by PALHUB01.lsi.com (128.94.213.114) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 16 Jan 2012 00:21:55 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch01.lsi.com ([135.36.98.37]) with mapi; Mon, 16 Jan 2012 10:51:52 +0530 From: "Desai, Kashyap" To: "Kenneth D. Merry" , John Date: Mon, 16 Jan 2012 10:51:42 +0530 Thread-Topic: mps driver chain_alloc_fail / performance ? Thread-Index: AczTFsTZz77NBltcTZiZx+nRPz9abAA93exQ Message-ID: References: <20120114051618.GA41288@FreeBSD.org> <20120114232245.GA57880@nargothrond.kdm.org> In-Reply-To: <20120114232245.GA57880@nargothrond.kdm.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" Subject: RE: mps driver chain_alloc_fail / performance ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2012 05:32:50 -0000 Which driver version is this ? In our 09.00.00.00 Driver (which is in pipel= ine to be committed) has 2048 chain buffer counter. And our Test team has verified it with almost 150+ Drives. As suggested by Ken, Can you try increasing MPS_CHAIN_FRAMES to 4096 OR 20= 48 ~ Kashyap > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of Kenneth D. Merry > Sent: Sunday, January 15, 2012 4:53 AM > To: John > Cc: freebsd-scsi@freebsd.org > Subject: Re: mps driver chain_alloc_fail / performance ? >=20 > On Sat, Jan 14, 2012 at 05:16:18 +0000, John wrote: > > Hi Folks, > > > > I've started poking through the source for this, but thought I'd > > go ahead and post to ask other's their opinion. > > > > I have a system with 3 LSI SAS hba cards installed: > > > > mps0: port 0x5000-0x50ff mem 0xf5ff0000- > 0xf5ff3fff,0xf5f80000-0xf5fbffff irq 30 at device 0.0 on pci13 > > mps0: Firmware: 05.00.13.00 > > mps0: IOCCapabilities: > 285c > > mps1: port 0x7000-0x70ff mem 0xfbef0000- > 0xfbef3fff,0xfbe80000-0xfbebffff irq 48 at device 0.0 on pci33 > > mps1: Firmware: 07.00.00.00 > > mps1: IOCCapabilities: > 1285c c> > > mps2: port 0x6000-0x60ff mem 0xfbcf0000- > 0xfbcf3fff,0xfbc80000-0xfbcbffff irq 56 at device 0.0 on pci27 > > mps2: Firmware: 07.00.00.00 > > mps2: IOCCapabilities: > 1285c c> >=20 > The firmware on those boards is a little old. You might consider > upgrading. >=20 > > Basically, one for internal and two for external drives, for a > total > > of about 200 drives, ie: > > > > # camcontrol inquiry da10 > > pass21: Fixed Direct Access SCSI-5 device > > pass21: Serial Number 6XR14KYV0000B148LDKM > > pass21: 600.000MB/s transfers, Command Queueing Enabled >=20 > That's a lot of drives! I've only run up to 60 drives. >=20 > > When running the system under load, I see the following reported: > > > > hw.mps.0.allow_multiple_tm_cmds: 0 > > hw.mps.0.io_cmds_active: 0 > > hw.mps.0.io_cmds_highwater: 772 > > hw.mps.0.chain_free: 2048 > > hw.mps.0.chain_free_lowwater: 1832 > > hw.mps.0.chain_alloc_fail: 0 <--- Ok > > > > hw.mps.1.allow_multiple_tm_cmds: 0 > > hw.mps.1.io_cmds_active: 0 > > hw.mps.1.io_cmds_highwater: 1019 > > hw.mps.1.chain_free: 2048 > > hw.mps.1.chain_free_lowwater: 0 > > hw.mps.1.chain_alloc_fail: 14369 <---- ?? > > > > hw.mps.2.allow_multiple_tm_cmds: 0 > > hw.mps.2.io_cmds_active: 0 > > hw.mps.2.io_cmds_highwater: 1019 > > hw.mps.2.chain_free: 2048 > > hw.mps.2.chain_free_lowwater: 0 > > hw.mps.2.chain_alloc_fail: 13307 <---- ?? > > > > So finally my question (sorry, I'm long winded): What is the > > correct way to increase the number of elements in sc->chain_list > > so mps_alloc_chain() won't run out? >=20 > Bump MPS_CHAIN_FRAMES to something larger. You can try 4096 and see > what > happens. >=20 > > static __inline struct mps_chain * > > mps_alloc_chain(struct mps_softc *sc) > > { > > struct mps_chain *chain; > > > > if ((chain =3D TAILQ_FIRST(&sc->chain_list)) !=3D NULL) { > > TAILQ_REMOVE(&sc->chain_list, chain, chain_link); > > sc->chain_free--; > > if (sc->chain_free < sc->chain_free_lowwater) > > sc->chain_free_lowwater =3D sc->chain_free; > > } else > > sc->chain_alloc_fail++; > > return (chain); > > } > > > > A few layers up, it seems like it would be nice if the buffer > > exhaustion was reported outside of debug being enabled... at least > > maybe the first time. >=20 > It used to report being out of chain frames every time it happened, > which > wound up being too much. You're right, doing it once might be good. >=20 > > It looks like changing the related #define is the only way. >=20 > Yes, that is currently the only way. Yours is by far the largest setup > I've seen so far. I've run the driver with 60 drives attached. >=20 > > Does anyone have any experience with tuning this driver for high > > throughput/large disk arrays? The shelves are all dual pathed, and > with > > the new gmultipath active/active support, I've still only been able to > > achieve about 500MBytes per second across the controllers/drives. >=20 > Once you bump up the number of chain frames to the point where you > aren't > running out, I doubt the driver will be the big bottleneck. It'll > probably > be other things higher up the stack. >=20 > > ps: I currently have a ccd on top of these drives which seems to > > perform more consistenty then zfs. But that's an email for a different > > day :-) >=20 > What sort of ZFS topology did you try? >=20 > I know for raidz2, and perhaps for raidz, ZFS is faster if your number > of > data disks is a power of 2. >=20 > If you want raidz2 protection, try creating arrays in groups of 10, so > you > wind up having 8 data disks. >=20 > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 16 11:07:11 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84D3B106564A for ; Mon, 16 Jan 2012 11:07:11 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 69D218FC2A for ; Mon, 16 Jan 2012 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0GB7BGi057757 for ; Mon, 16 Jan 2012 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0GB7A5Z057755 for freebsd-scsi@FreeBSD.org; Mon, 16 Jan 2012 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jan 2012 11:07:10 GMT Message-Id: <201201161107.q0GB7A5Z057755@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2012 11:07:11 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/163812 scsi [mpt] problem with mpt driver for lsi controlled conne o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c f kern/163130 scsi [mpt] cannot dumpon to mpt connected disk o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153514 scsi [cam] [panic] CAM related panic o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c s kern/149927 scsi [cam] hard drive not stopped before removing power dur o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o bin/57088 scsi [cam] [patch] for a possible fd leak in libcam.c o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 51 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 17 02:02:19 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CDB4106566B; Tue, 17 Jan 2012 02:02:19 +0000 (UTC) (envelope-from jwd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EF3BE8FC12; Tue, 17 Jan 2012 02:02:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0H22ISW090659; Tue, 17 Jan 2012 02:02:18 GMT (envelope-from jwd@freefall.freebsd.org) Received: (from jwd@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0H22IAp090658; Tue, 17 Jan 2012 02:02:18 GMT (envelope-from jwd) Date: Tue, 17 Jan 2012 02:02:18 +0000 From: John To: "Desai, Kashyap" , "Kenneth D. Merry" Message-ID: <20120117020218.GA59053@FreeBSD.org> References: <20120114051618.GA41288@FreeBSD.org> <20120114232245.GA57880@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "freebsd-scsi@freebsd.org" Subject: Re: mps driver chain_alloc_fail / performance ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 02:02:19 -0000 ----- Desai, Kashyap's Original Message ----- > Which driver version is this ? In our 09.00.00.00 Driver (which is in pipeline to be committed) has 2048 chain buffer counter. I'm not sure how to answer your question directly. We're using the driver that comes with FreeBSD. Not a driver directly from LSI. If we can get a copy of your 9.0 driver we can try testing against it. > And our Test team has verified it with almost 150+ Drives. Currently, we have 8 shelves, 25 drives per shelf, dual attached configured with geom multipath using Active/Active. Ignoring SSDs and OS disks on the internal card, we see 400 da devices on mps1 & mps2. For the record, the shelves are: ses0 at mps1 bus 0 scbus7 target 0 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 600.000MB/s transfers ses0: Command Queueing enabled ses0: SCSI-3 SES Device > As suggested by Ken, Can you try increasing MPS_CHAIN_FRAMES to 4096 OR 2048 Absolutely. The current value is 2048. We are currently running with this patch to increase the value and output a singular alerting message: --- sys/dev/mps/mpsvar.h.orig 2012-01-15 19:28:51.000000000 -0500 +++ sys/dev/mps/mpsvar.h 2012-01-15 20:14:07.000000000 -0500 @@ -34,7 +34,7 @@ #define MPS_REQ_FRAMES 1024 #define MPS_EVT_REPLY_FRAMES 32 #define MPS_REPLY_FRAMES MPS_REQ_FRAMES -#define MPS_CHAIN_FRAMES 2048 +#define MPS_CHAIN_FRAMES 4096 #define MPS_SENSE_LEN SSD_FULL_SIZE #define MPS_MSI_COUNT 1 #define MPS_SGE64_SIZE 12 @@ -242,8 +242,11 @@ sc->chain_free--; if (sc->chain_free < sc->chain_free_lowwater) sc->chain_free_lowwater = sc->chain_free; - } else + } else { sc->chain_alloc_fail++; + if (sc->chain_alloc_fail == 1) + device_printf(sc->mps_dev,"Insufficient chain_list buffers."); + } return (chain); } If the logic for outputting the message is appropriate I think it would be nice to get it committed. > ~ Kashyap > > > Kenneth D. Merry said: > > > > The firmware on those boards is a little old. You might consider > > upgrading. We updated the the FW this morning and we're now showing: mps0: port 0x5000-0x50ff mem 0xf5ff0000-0xf5ff3fff,0xf5f80000-0xf5fbffff irq 30 at device 0.0 on pci13 mps0: Firmware: 12.00.00.00 mps0: IOCCapabilities: 1285c mps1: port 0x7000-0x70ff mem 0xfbef0000-0xfbef3fff,0xfbe80000-0xfbebffff irq 48 at device 0.0 on pci33 mps1: Firmware: 12.00.00.00 mps1: IOCCapabilities: 1285c mps2: port 0x6000-0x60ff mem 0xfbcf0000-0xfbcf3fff,0xfbc80000-0xfbcbffff irq 56 at device 0.0 on pci27 mps2: Firmware: 12.00.00.00 mps2: IOCCapabilities: 1285c We last updated about around November of last year. > > > # camcontrol inquiry da10 > > > pass21: Fixed Direct Access SCSI-5 device > > > pass21: Serial Number 6XR14KYV0000B148LDKM > > > pass21: 600.000MB/s transfers, Command Queueing Enabled > > > > That's a lot of drives! I've only run up to 60 drives. See above. In general, I'm relatively pleased with how the system responds with all these drives. > > > When running the system under load, I see the following reported: > > > > > > hw.mps.2.allow_multiple_tm_cmds: 0 > > > hw.mps.2.io_cmds_active: 0 > > > hw.mps.2.io_cmds_highwater: 1019 > > > hw.mps.2.chain_free: 2048 > > > hw.mps.2.chain_free_lowwater: 0 > > > hw.mps.2.chain_alloc_fail: 13307 <---- ?? The current test case run is showing: hw.mps.2.debug_level: 0 hw.mps.2.allow_multiple_tm_cmds: 0 hw.mps.2.io_cmds_active: 109 hw.mps.2.io_cmds_highwater: 1019 hw.mps.2.chain_free: 4042 hw.mps.2.chain_free_lowwater: 3597 hw.mps.2.chain_alloc_fail: 0 It may be a few hours before it progresses to the point where it ran low last time. > > Bump MPS_CHAIN_FRAMES to something larger. You can try 4096 and see > > what happens. Agreed. Let me know if you thing there is anything we should add to the patch above. > > > A few layers up, it seems like it would be nice if the buffer > > > exhaustion was reported outside of debug being enabled... at least > > > maybe the first time. > > > > It used to report being out of chain frames every time it happened, > > which wound up being too much. You're right, doing it once might be good. Thanks, that's how I tried to put the patch together. > > Once you bump up the number of chain frames to the point where you aren't > > running out, I doubt the driver will be the big bottleneck. It'll probably > > be other things higher up the stack. Question. What "should" the layer of code above the mps driver do if the driver returns ENOBUFS? I'm wondering if it might explain some incorrect results. > > What sort of ZFS topology did you try? > > > > I know for raidz2, and perhaps for raidz, ZFS is faster if your number > > of data disks is a power of 2. > > > > If you want raidz2 protection, try creating arrays in groups of 10, so > > you wind up having 8 data disks. The fasted we've seen is with a pool made of mirrors, though this uses up the most space. It also caused the most alloc fails (and leads to my question about ENOBUFS). Thank you both for your help. Any comments are always welcome! If I haven't answered a question, or otherwise said something that doesn't make sense, let me know. Thanks, John From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 17 05:13:18 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6151A106566C for ; Tue, 17 Jan 2012 05:13:18 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 191D68FC16 for ; Tue, 17 Jan 2012 05:13:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id 292962041B2 for ; Tue, 17 Jan 2012 06:13:15 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kt0z+meLhgsg for ; Tue, 17 Jan 2012 06:13:14 +0100 (CET) Received: from [192.168.48.66] (unknown [216.99.48.229]) by smtp.infotech.no (Postfix) with ESMTPA id B15CD204119 for ; Tue, 17 Jan 2012 06:13:13 +0100 (CET) Message-ID: <4F150368.4040802@interlog.com> Date: Tue, 17 Jan 2012 00:13:12 -0500 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: "freebsd-scsi@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: man page difficulties in FreeBSD 9 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 05:13:18 -0000 While testing my SCSI packages with FreeBSD 9 (e.g. sg3_utils and smp_utils), the man pages have gone missing. Using a standard "./configure ; make ; make install" everything is placed in /usr/local as that seems to be the BSD way. The executables are found in the /usr/local/bin directory but the man pages go into the /usr/local/share/man directory which may as well be a black hole since /usr/local/share/man is not on the standard manpath. There are lots of possible hacks to make this work, for example: ./configure --mandir=/usr/local but that is ugly. My temporary solution is to add this file: # cat /usr/local/etc/man.d/expletive.conf MANPATH /usr/local/share/man Can't remember this happening in FreeBSD 8. Doug Gilbert From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 17 13:43:08 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FAD71065673 for ; Tue, 17 Jan 2012 13:43:08 +0000 (UTC) (envelope-from pkeusem@visi.com) Received: from g2host.com (mailfront4.g2host.com [208.42.184.242]) by mx1.freebsd.org (Postfix) with ESMTP id CE9948FC13 for ; Tue, 17 Jan 2012 13:43:07 +0000 (UTC) Received: from [173.30.51.17] (account pkeusem@visi.com HELO [172.16.175.217]) by mailfront4.g2host.com (CommuniGate Pro SMTP 5.3.11) with ESMTPSA id 44072970; Tue, 17 Jan 2012 07:23:05 -0600 Message-ID: <4F157637.502@visi.com> Date: Tue, 17 Jan 2012 07:23:03 -0600 From: Paul Keusemann User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:8.0) Gecko/20111106 Thunderbird/8.0 MIME-Version: 1.0 To: dgilbert@interlog.com References: <4F150368.4040802@interlog.com> In-Reply-To: <4F150368.4040802@interlog.com> X-Is-From-Me: yes Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-scsi@freebsd.org" Subject: Re: man page difficulties in FreeBSD 9 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 13:43:08 -0000 On 01/16/12 23:13, Douglas Gilbert wrote: > While testing my SCSI packages with FreeBSD 9 (e.g. sg3_utils > and smp_utils), the man pages have gone missing. > > Using a standard "./configure ; make ; make install" everything > is placed in /usr/local as that seems to be the BSD way. The > executables are found in the /usr/local/bin directory but the > man pages go into the /usr/local/share/man directory which may as > well be a black hole since /usr/local/share/man is not on the > standard manpath. > > There are lots of possible hacks to make this work, for example: > ./configure --mandir=/usr/local > but that is ugly. My temporary solution is to add this file: > # cat /usr/local/etc/man.d/expletive.conf > MANPATH /usr/local/share/man You could also add an OPTIONAL_MANPATH entry to /etc/manpath.config, assuming you are using the manpath command to set your MANPATH. Just make sure you unset the MANPATH environment variable before running the manpath command. > > Can't remember this happening in FreeBSD 8. > > Doug Gilbert > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > -- Paul Keusemann pkeusem@visi.com 4266 Joppa Court (952) 894-7805 Savage, MN 55378 From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 18 04:30:11 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 659F9106566C; Wed, 18 Jan 2012 04:30:11 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog102.obsmtp.com (na3sys009aog102.obsmtp.com [74.125.149.69]) by mx1.freebsd.org (Postfix) with ESMTP id 8841C8FC08; Wed, 18 Jan 2012 04:30:10 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob102.postini.com ([74.125.148.12]) with SMTP ID DSNKTxZK0e5+VuEP+aZQcfDAHmnW2V0a4vwr@postini.com; Tue, 17 Jan 2012 20:30:10 PST Received: from PALHUB01.lsi.com (128.94.213.114) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.137.0; Tue, 17 Jan 2012 23:34:07 -0500 Received: from inbexch01.lsi.com (135.36.98.37) by PALHUB01.lsi.com (128.94.213.114) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 17 Jan 2012 23:30:09 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch01.lsi.com ([135.36.98.37]) with mapi; Wed, 18 Jan 2012 10:00:07 +0530 From: "Desai, Kashyap" To: John , "Kenneth D. Merry" Date: Wed, 18 Jan 2012 10:00:05 +0530 Thread-Topic: mps driver chain_alloc_fail / performance ? Thread-Index: AczUvA8r1tfJdh1fTf+THv3LhyAfiAA2/q5g Message-ID: References: <20120114051618.GA41288@FreeBSD.org> <20120114232245.GA57880@nargothrond.kdm.org> <20120117020218.GA59053@FreeBSD.org> In-Reply-To: <20120117020218.GA59053@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" Subject: RE: mps driver chain_alloc_fail / performance ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2012 04:30:11 -0000 > -----Original Message----- > From: John [mailto:jwd@freebsd.org] > Sent: Tuesday, January 17, 2012 7:32 AM > To: Desai, Kashyap; Kenneth D. Merry > Cc: freebsd-scsi@freebsd.org > Subject: Re: mps driver chain_alloc_fail / performance ? >=20 > ----- Desai, Kashyap's Original Message ----- > > Which driver version is this ? In our 09.00.00.00 Driver (which is in > pipeline to be committed) has 2048 chain buffer counter. >=20 > I'm not sure how to answer your question directly. We're using the > driver > that comes with FreeBSD. Not a driver directly from LSI. If we can get a > copy > of your 9.0 driver we can try testing against it. If you type "sysctl -a |grep mps" you can see driver version.. >=20 > > And our Test team has verified it with almost 150+ Drives. >=20 > Currently, we have 8 shelves, 25 drives per shelf, dual attached > configured with geom multipath using Active/Active. Ignoring SSDs and > OS disks on the internal card, we see 400 da devices on mps1 & mps2. > For the record, the shelves are: >=20 > ses0 at mps1 bus 0 scbus7 target 0 lun 0 > ses0: Fixed Enclosure Services SCSI-5 device > ses0: 600.000MB/s transfers > ses0: Command Queueing enabled > ses0: SCSI-3 SES Device >=20 >=20 > > As suggested by Ken, Can you try increasing MPS_CHAIN_FRAMES to 4096 > OR 2048 >=20 > Absolutely. The current value is 2048. We are currently running with > this patch to increase the value and output a singular alerting message: >=20 > --- sys/dev/mps/mpsvar.h.orig 2012-01-15 19:28:51.000000000 -0500 > +++ sys/dev/mps/mpsvar.h 2012-01-15 20:14:07.000000000 -0500 > @@ -34,7 +34,7 @@ > #define MPS_REQ_FRAMES 1024 > #define MPS_EVT_REPLY_FRAMES 32 > #define MPS_REPLY_FRAMES MPS_REQ_FRAMES > -#define MPS_CHAIN_FRAMES 2048 > +#define MPS_CHAIN_FRAMES 4096 > #define MPS_SENSE_LEN SSD_FULL_SIZE > #define MPS_MSI_COUNT 1 > #define MPS_SGE64_SIZE 12 > @@ -242,8 +242,11 @@ > sc->chain_free--; > if (sc->chain_free < sc->chain_free_lowwater) > sc->chain_free_lowwater =3D sc->chain_free; > - } else > + } else { > sc->chain_alloc_fail++; > + if (sc->chain_alloc_fail =3D=3D 1) > + device_printf(sc->mps_dev,"Insufficient chain_list > buffers."); > + } > return (chain); > } >=20 >=20 > If the logic for outputting the message is appropriate I think > it would be nice to get it committed. If this works for you and you really want to commit, I would suggest to hav= e module parameter to pass chain_max value. Basically, current implementation is not the correct way to handle out of c= hain scenario. Driver should calculate max chain required per HBA at run time from IOC fac= t reply from FW. And it should try to allocate those many Chain buffer run time (instead of having #define for chain max ).=20 If Driver does not find those memory from system @ run time, we should fail= to detect HBA at load time. >From our Linux Driver logs, I find out we need 29700 chain buffer required = per HBA(SAS2008 PCI-Express). So better to increase MPS_CHAIN_FRAMES to (24 * 1024), until we have more r= obust support in driver. Hope this helps you. ~ Kashyap >=20 > > ~ Kashyap > > > > > Kenneth D. Merry said: > > > > > > The firmware on those boards is a little old. You might consider > > > upgrading. >=20 > We updated the the FW this morning and we're now showing: >=20 > mps0: port 0x5000-0x50ff mem 0xf5ff0000- > 0xf5ff3fff,0xf5f80000-0xf5fbffff irq 30 at device 0.0 on pci13 > mps0: Firmware: 12.00.00.00 > mps0: IOCCapabilities: > 1285c c> > mps1: port 0x7000-0x70ff mem 0xfbef0000- > 0xfbef3fff,0xfbe80000-0xfbebffff irq 48 at device 0.0 on pci33 > mps1: Firmware: 12.00.00.00 > mps1: IOCCapabilities: > 1285c c> > mps2: port 0x6000-0x60ff mem 0xfbcf0000- > 0xfbcf3fff,0xfbc80000-0xfbcbffff irq 56 at device 0.0 on pci27 > mps2: Firmware: 12.00.00.00 > mps2: IOCCapabilities: > 1285c c> >=20 > We last updated about around November of last year. >=20 > > > > # camcontrol inquiry da10 > > > > pass21: Fixed Direct Access SCSI-5 device > > > > pass21: Serial Number 6XR14KYV0000B148LDKM > > > > pass21: 600.000MB/s transfers, Command Queueing Enabled > > > > > > That's a lot of drives! I've only run up to 60 drives. >=20 > See above. In general, I'm relatively pleased with how the system > responds with all these drives. >=20 > > > > When running the system under load, I see the following > reported: > > > > > > > > hw.mps.2.allow_multiple_tm_cmds: 0 > > > > hw.mps.2.io_cmds_active: 0 > > > > hw.mps.2.io_cmds_highwater: 1019 > > > > hw.mps.2.chain_free: 2048 > > > > hw.mps.2.chain_free_lowwater: 0 > > > > hw.mps.2.chain_alloc_fail: 13307 <---- ?? >=20 > The current test case run is showing: >=20 > hw.mps.2.debug_level: 0 > hw.mps.2.allow_multiple_tm_cmds: 0 > hw.mps.2.io_cmds_active: 109 > hw.mps.2.io_cmds_highwater: 1019 > hw.mps.2.chain_free: 4042 > hw.mps.2.chain_free_lowwater: 3597 > hw.mps.2.chain_alloc_fail: 0 >=20 > It may be a few hours before it progresses to the point where it > ran low last time. >=20 > > > Bump MPS_CHAIN_FRAMES to something larger. You can try 4096 and see > > > what happens. >=20 > Agreed. Let me know if you thing there is anything we should add to > the patch above. >=20 > > > > A few layers up, it seems like it would be nice if the buffer > > > > exhaustion was reported outside of debug being enabled... at least > > > > maybe the first time. > > > > > > It used to report being out of chain frames every time it happened, > > > which wound up being too much. You're right, doing it once might be > good. >=20 > Thanks, that's how I tried to put the patch together. >=20 > > > Once you bump up the number of chain frames to the point where you > aren't > > > running out, I doubt the driver will be the big bottleneck. It'll > probably > > > be other things higher up the stack. >=20 > Question. What "should" the layer of code above the mps driver do if the > driver > returns ENOBUFS? I'm wondering if it might explain some incorrect > results. >=20 > > > What sort of ZFS topology did you try? > > > > > > I know for raidz2, and perhaps for raidz, ZFS is faster if your > number > > > of data disks is a power of 2. > > > > > > If you want raidz2 protection, try creating arrays in groups of 10, > so > > > you wind up having 8 data disks. >=20 > The fasted we've seen is with a pool made of mirrors, though this uses > up the most space. It also caused the most alloc fails (and leads to my > question about ENOBUFS). >=20 > Thank you both for your help. Any comments are always welcome! If I > haven't > answered a question, or otherwise said something that doesn't make > sense, let me know. >=20 > Thanks, > John From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 20 20:45:01 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18BC8106564A; Fri, 20 Jan 2012 20:45:01 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id B3A008FC0A; Fri, 20 Jan 2012 20:45:00 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q0KKixXV054048; Fri, 20 Jan 2012 13:44:59 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q0KKixV5054047; Fri, 20 Jan 2012 13:44:59 -0700 (MST) (envelope-from ken) Date: Fri, 20 Jan 2012 13:44:59 -0700 From: "Kenneth D. Merry" To: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Message-ID: <20120120204459.GA51162@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Cc: Subject: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 20:45:01 -0000 The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is available here: http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt I plan to check it in to head next week, and then MFC it into stable/9 a week after that most likely. Please test it out and let me know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! I have added a number of other infrastructure changes that are necessary for the driver, and here is a brief summary: - A new Advanced Information buffer is now added to the EDT for drives that support READ CAPACITY (16). The da(4) driver updates this buffer when it grabs new read capacity data from a drive. - The mps(4) driver will look for Advanced Information state change async events, and updates its table of drives with protection information turned on accordingly. - The size of struct scsi_read_capacity_data_long has been bumped up to the amount specified in the latest SBC-3 draft. The hope is to avoid some future structure size bumps with that change. The API for scsi_read_capacity_16() has been changed to add a length argument. Hopefully this will future-proof it somewhat. - __FreeBSD_version bumped for the addition of the Advanced Information buffer with the read capacity information. The mps(4) driver has a kludgy way of getting the information on versions of FreeBSD without this change. I believe that the CAM API changes are mild enough and beneficial enough for a merge into stable/9, but they are intertwined with the unmap changes in the da(4) driver, so those changes will have to go back to stable/9 as well in order to MFC the full set of changes. Otherwise it'll just be the driver that gets merged into stable/9, and it'll use the kludgy method of getting the read capacity data for each drive. A couple of notes about issues with this driver: - Unlike the current mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the driver in the tree has the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 20 21:01:01 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2431D106564A; Fri, 20 Jan 2012 21:01:01 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id E0B578FC12; Fri, 20 Jan 2012 21:01:00 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q0KL1070056044; Fri, 20 Jan 2012 14:01:00 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q0KL10DA056043; Fri, 20 Jan 2012 14:01:00 -0700 (MST) (envelope-from ken) Date: Fri, 20 Jan 2012 14:01:00 -0700 From: "Kenneth D. Merry" To: Freddie Cash Message-ID: <20120120210059.GA55103@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 21:01:01 -0000 On Fri, Jan 20, 2012 at 12:53:04 -0800, Freddie Cash wrote: > On Fri, Jan 20, 2012 at 12:44 PM, Kenneth D. Merry wrote: > > The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > > HBAs as well as WarpDrive controllers, is available here: > > Just to clarify, this will replace the existing mps(4) driver in > FreeBSD 10-CURRENT and 9-STABLE? That is correct. > So there won't be mps(4) (FreeBSD driver) and mpslsi(4) (LSI driver) > anymore? Just mps(4)? Right. Just mps(4), which will be the LSI driver. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 20 21:15:15 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D804106564A; Fri, 20 Jan 2012 21:15:15 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id D2E998FC08; Fri, 20 Jan 2012 21:15:14 +0000 (UTC) Received: by vcbfl17 with SMTP id fl17so1096668vcb.13 for ; Fri, 20 Jan 2012 13:15:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EmBcprK3fiqEDT5lg5agp4cN/ZCi3mNtKRu2dTHMhV4=; b=Yxj7FHSQomZYd/mLzmehhrQpRxXtCe1xX25Azau/0eTKnKQGMcRWLEnr7j4L7qnnL8 kfgJ1Yh94OxrM60OO0wV9N5cTdRMexLqTOl4u8DhKhOvbpRChijiVC22Q1CwLldsxy4x eMMCJ2S1D4Idee4YlhwloH8eNUjiwL2ZPfh8Q= MIME-Version: 1.0 Received: by 10.221.13.196 with SMTP id pn4mr20071143vcb.74.1327092784089; Fri, 20 Jan 2012 12:53:04 -0800 (PST) Received: by 10.220.117.11 with HTTP; Fri, 20 Jan 2012 12:53:04 -0800 (PST) In-Reply-To: <20120120204459.GA51162@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> Date: Fri, 20 Jan 2012 12:53:04 -0800 Message-ID: From: Freddie Cash To: "Kenneth D. Merry" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 21:15:15 -0000 On Fri, Jan 20, 2012 at 12:44 PM, Kenneth D. Merry wrote: > The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > HBAs as well as WarpDrive controllers, is available here: Just to clarify, this will replace the existing mps(4) driver in FreeBSD 10-CURRENT and 9-STABLE? So there won't be mps(4) (FreeBSD driver) and mpslsi(4) (LSI driver) anymore? Just mps(4)? -- Freddie Cash fjwcash@gmail.com From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 20 23:24:45 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91EE11065677; Fri, 20 Jan 2012 23:24:45 +0000 (UTC) (envelope-from prvs=13668cec48=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B8E1C8FC0C; Fri, 20 Jan 2012 23:24:44 +0000 (UTC) X-Spam-Processed: mail1.multiplay.co.uk, Fri, 20 Jan 2012 23:14:13 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50017643641.msg; Fri, 20 Jan 2012 23:14:11 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=13668cec48=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> From: "Steven Hartland" To: "Kenneth D. Merry" , , References: <20120120204459.GA51162@nargothrond.kdm.org> Date: Fri, 20 Jan 2012 23:14:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 23:24:45 -0000 ----- Original Message ----- From: "Kenneth D. Merry" To: ; Sent: Friday, January 20, 2012 8:44 PM Subject: LSI supported mps(4) driver available > > The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > HBAs as well as WarpDrive controllers, is available here: > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > I plan to check it in to head next week, and then MFC it into stable/9 a > week after that most likely. Great to see this being done, thanks to everyone! Be even better to see this MFC'ed to 8.x as well if all goes well. Do you think this will possible? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 20 23:28:43 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22E79106566B; Fri, 20 Jan 2012 23:28:43 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id E2EF98FC16; Fri, 20 Jan 2012 23:28:42 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q0KNSgvC071893; Fri, 20 Jan 2012 16:28:42 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q0KNSgg7071892; Fri, 20 Jan 2012 16:28:42 -0700 (MST) (envelope-from ken) Date: Fri, 20 Jan 2012 16:28:42 -0700 From: "Kenneth D. Merry" To: Steven Hartland Message-ID: <20120120232841.GA71874@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 23:28:43 -0000 On Fri, Jan 20, 2012 at 23:14:20 -0000, Steven Hartland wrote: > ----- Original Message ----- > From: "Kenneth D. Merry" > To: ; > Sent: Friday, January 20, 2012 8:44 PM > Subject: LSI supported mps(4) driver available > > > > > >The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > >HBAs as well as WarpDrive controllers, is available here: > > > >http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > > >I plan to check it in to head next week, and then MFC it into stable/9 a > >week after that most likely. > > Great to see this being done, thanks to everyone! Be even better to see > this MFC'ed to 8.x as well if all goes well. Do you think this will > possible? Yes, that should be doable as well. It's unlikely that all of the CAM changes will get merged back, but the driver itself shouldn't be a problem. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 21 00:39:46 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4F6A106564A; Sat, 21 Jan 2012 00:39:46 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 471CF8FC1D; Sat, 21 Jan 2012 00:39:45 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-122-214.lns20.adl2.internode.on.net [118.210.122.214]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id q0L0O8cl072565 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 21 Jan 2012 10:54:14 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20120120204459.GA51162@nargothrond.kdm.org> Date: Sat, 21 Jan 2012 10:54:08 +1030 Content-Transfer-Encoding: 7bit Message-Id: References: <20120120204459.GA51162@nargothrond.kdm.org> To: "Kenneth D. Merry" X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.16 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 00:39:46 -0000 On 21/01/2012, at 7:14, Kenneth D. Merry wrote: > In addition to supporting WarpDrive, the driver also supports Integrated > RAID. > > Thanks to LSI for doing the work on this driver! This is great news (the RAID support) - thanks very much. Is there a corresponding userland tool, or plans for one? Thanks again. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 21 01:43:51 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 036D9106566B; Sat, 21 Jan 2012 01:43:51 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B1B008FC12; Sat, 21 Jan 2012 01:43:50 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so2136218obc.13 for ; Fri, 20 Jan 2012 17:43:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0y2n7DJDYke6raqKuSD4kjN625/Mo1g8/GQOhyYGI3w=; b=EJ8BeknbTR32Y4mLxqn+9GQEVZwVgbW3ClbHyPMx+SroFMWhChVYoTXDD+xxBobpOA yRCb/0Dg914Zo/oeI8TE+ioenab2WppmXDGnC94TUZMUrEJKoo7F0JrNgxYDeBD9BU30 K3g8Tb0S0P2tALEQ9Rnj5u8XRWvPzyRHSGNsU= MIME-Version: 1.0 Received: by 10.182.222.102 with SMTP id ql6mr136608obc.2.1327108650366; Fri, 20 Jan 2012 17:17:30 -0800 (PST) Received: by 10.182.225.100 with HTTP; Fri, 20 Jan 2012 17:17:30 -0800 (PST) In-Reply-To: <20120120232841.GA71874@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> Date: Fri, 20 Jan 2012 18:17:30 -0700 Message-ID: From: Jason Wolfe To: "Kenneth D. Merry" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-scsi@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 01:43:51 -0000 On Fri, Jan 20, 2012 at 4:28 PM, Kenneth D. Merry wrote: > On Fri, Jan 20, 2012 at 23:14:20 -0000, Steven Hartland wrote: > > ----- Original Message ----- > > From: "Kenneth D. Merry" > > To: ; > > Sent: Friday, January 20, 2012 8:44 PM > > Subject: LSI supported mps(4) driver available > > > > > > > > > >The LSI-supported version of the mps(4) driver that supports their 6Gb > SAS > > >HBAs as well as WarpDrive controllers, is available here: > > > > > >http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > > > > >I plan to check it in to head next week, and then MFC it into stable/9 a > > >week after that most likely. > > > > Great to see this being done, thanks to everyone! Be even better to see > > this MFC'ed to 8.x as well if all goes well. Do you think this will > > possible? > > Yes, that should be doable as well. It's unlikely that all of the CAM > changes will get merged back, but the driver itself shouldn't be a problem. > > Ken > Just in case this needs a bit more fuel, bringing it back to 8.x would be quite welcome for many who are having issues with the bugs in the current driver. One of the more troubling being smartctl having the ability to crash a system when run on a disk with tags > 2. I had started up a thread back in Nov regarding it and found that the LSI binary driver did in fact handle the issue gracefully - http://lists.freebsd.org/pipermail/freebsd-scsi/2011-November/005091.html. Thank you sir! Jason Wolfe