From owner-freebsd-scsi@freebsd.org Sun Dec 13 02:33:09 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9C54A14C0B for ; Sun, 13 Dec 2015 02:33:09 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 955951788 for ; Sun, 13 Dec 2015 02:33:09 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by qkht125 with SMTP id t125so92303403qkh.3 for ; Sat, 12 Dec 2015 18:33:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T+RQlhMuijt1v9jI5dOPnf4AD2UnK34CBCu1TmJAuYc=; b=q+ThG4a7lnWXzvBxr35JjuixRhHMbOwOymk0RNhha03Mp6632F/j5Iu5eEHAmu7pAC gbJ7OnsWrqMLm2i9LaxwidhL/G9n5MZkQ4IqEvCPZSFOs/TjaIn9Kx+pB+O5ejv/m//o nIkK37VSNClvrUlDuVPA8hpry48NuCraB0eGM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=T+RQlhMuijt1v9jI5dOPnf4AD2UnK34CBCu1TmJAuYc=; b=hkxxKUGFt4W6Y2ppEmSZX93bmYmvyYVsKXUsIBfJC52jb/zcM6w60gdWMfrJTt+4sI +q3CP0eLKyAJvMEeB49oJD3mqhuZLpdFmwsomCfuZ6Q9wYhPrgHbgfN4/WaTX7qcVkgG ovdxFsQ8HWksV3jaxQGA0tC5AtEmXRQjB2I213ZhsAqg6Z+xn35Ij26zeBOXpinuiXlO QsAdeoJAgaBXxA2ymjuTiCeyVOqtCnf6h+rL4e7LuWeLtwt8LVkyYkKx5fRno4BispwC TmYNZKH+llgWRiAKi9XNJGl5p97vkBc1ZOe8YOww2jpvw1s8eu9KqsNh36DKDU4Mqceu xmjQ== X-Gm-Message-State: ALoCoQldT9lU8gvdW0F0p7VZKvdsMntQmyuM1mpBYWHSGKqINlMKZNbzK/qdXdlZVAWXRBQjkUW2jYAXpYVz3eGN65G426XG0A== MIME-Version: 1.0 X-Received: by 10.129.81.147 with SMTP id f141mr14631115ywb.176.1449973988525; Sat, 12 Dec 2015 18:33:08 -0800 (PST) Received: by 10.37.13.147 with HTTP; Sat, 12 Dec 2015 18:33:08 -0800 (PST) In-Reply-To: References: <566B4F68.2040807@mWare.ca> <566B8E2A.8070404@mWare.ca> <566BC34D.2020404@mware.ca> Date: Sat, 12 Dec 2015 19:33:08 -0700 Message-ID: Subject: Re: Informal(?) sesX messages From: Kevin Bowling To: Alan Somers Cc: Mike Geiger , FreeBSD-scsi , Sean Bruno , jason@llnw.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2015 02:33:09 -0000 JFWIW we see this across a lot of our machines as well -- just arrival messages, usually some time well after the machine is fully booted. Dr. Google shows other instances. It appears to be harmless but noisy. root@cds124.lab:~# sysctl dev.mps.0.firmware_version dev.mps.0.firmware_version: 16.00.01.00 root@cds124.lab:~# sg_inq --hex --len=64 ses0 00 0d 00 05 02 34 00 40 02 4c 53 49 20 20 20 20 20 ....4.@.LSI 10 53 41 53 32 58 32 38 20 20 20 20 20 20 20 20 20 SAS2X28 20 30 65 31 32 78 33 36 2d 35 35 2e 31 34 2e 31 38 0e12x36-55.14.18 30 2e 30 00 20 20 20 20 20 .0. On Sat, Dec 12, 2015 at 8:41 AM, Alan Somers wrote: > On Fri, Dec 11, 2015 at 11:48 PM, wrote: > > On 2015/12/11 22:55, Alan Somers wrote: > >> > >> On Fri, Dec 11, 2015 at 8:02 PM, wrote: > >>> > >>> On 15-12-11 17:44, Alan Somers wrote: > >>>> > >>>> On Fri, Dec 11, 2015 at 3:34 PM, wrote: > >>>>> > >>>>> Hi all, please CC me on reply as I'm not subscribed to this list. > >>>>> > >>>>> I've got one of those Supermicro 72-drive monster machines, all ZFS'd > >>>>> up. > >>>>> > >>>>> > https://www.supermicro.com/products/system/4u/6048/SSG-6048R-E1CR72L.cfm > >>>>> > >>>>> And before & after replacing a faulty SAS Expander and a pair of > cables > >>>>> (gobs of WRITE/ABORT errors), I'm still occasionally seeing these > >>>>> kernel > >>>>> messages (in groups), and I'm not sure if they're benign, or pointing > >>>>> to > >>>>> a > >>>>> SAS expander event... or what. I admit, this is my first time dealing > >>>>> with a > >>>>> machine with SAS expanders, so I'm a bit out of my depth in diagnosis > >>>>> thereof. > >>>>> > >>>>> Dec 11 16:06:54 ZFS-AF kernel: ses5: da7,pass7: Element descriptor: > >>>>> 'Slot00' > >>>>> Dec 11 16:06:54 ZFS-AF kernel: ses5: da7,pass7: SAS Device Slot > >>>>> Element: > >>>>> 1 > >>>>> Phys at Slot 0 > >>>>> Dec 11 16:06:54 ZFS-AF kernel: ses5: phy 0: SAS device type 1 id 0 > >>>>> Dec 11 16:06:54 ZFS-AF kernel: ses5: phy 0: protocols: Initiator( > None > >>>>> ) > >>>>> Target( SSP ) > >>>>> Dec 11 16:06:54 ZFS-AF kernel: ses5: phy 0: parent 500304801ea2df3f > >>>>> addr > >>>>> 5000c500844bd449 > >>>>> > >>>> These look like device arrival notifications. If you scroll up, do > >>>> you see any departure notifications? They should look like this: > >>>> > >>>> mps0: mpssas_prepare_remove: Sending reset for target ID 10 > >>>> da0 at mps0 bus 0 scbus0 target 10 lun 0 > >>>> da0: s/n JPW930HQ15H26H detached > >>>> mps0: Unfreezing devq for target ID 10 > >>>> xpt_release_devq(): requested 1 > present 0 > >>>> (da0:mps0:0:10:0): Periph destroyed > >>>> > >>>> Also, could you post your HBA and expander firmware versions? > >>>> > >>>> -Alan > >>> > >>> > >>> I can say, without doubt, that I do NOT have any preceding > detachments... > >>> which is why I'm so baffled by the messages. If the devices aren't > >>> de/reattaching, what's the point of these informal/benign ones? I am > >>> familiar with them from other hot-swap and disk failure scenarios in > >>> other > >>> machines. > >>> > >>> Could this be a driver bug not logging the disconnection? But when I > >>> hot-unplugged them, I do see that in dmesg. > >>> Or does SAS do something where it might renegotiate or reconfigure the > >>> lanes, and I'm just seeing it do that? > >>> > >>> Thanks, > >>> > >>> Myke > >>> > >>> > >>> dev.mpr.0.driver_version: 09.255.01.00-fbsd > >>> dev.mpr.0.firmware_version: 06.00.00.00 > >>> dev.mpr.1.driver_version: 09.255.01.00-fbsd > >>> dev.mpr.1.firmware_version: 08.00.00.00 > >>> dev.mpr.2.driver_version: 09.255.01.00-fbsd > >>> dev.mpr.2.firmware_version: 08.00.00.00 > >>> > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses0 > >>> 00 0d 00 05 02 33 00 40 02 4c 53 49 20 20 20 20 20 ....3.@.LSI > >>> 10 53 41 53 33 78 34 38 20 20 20 20 20 20 20 20 20 SAS3x48 > >>> 20 30 37 30 31 78 34 38 2d 36 36 2e 37 2e 31 2e 31 > >>> 0701x48-66.7.1.1 > >>> 30 37 00 20 20 20 20 20 20 7. > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses1 > >>> 00 0d 00 05 02 33 00 40 02 4c 53 49 20 20 20 20 20 ....3.@.LSI > >>> 10 53 41 53 33 78 33 36 20 20 20 20 20 20 20 20 20 SAS3x36 > >>> 20 30 37 30 31 78 33 36 2d 36 36 2e 37 2e 31 2e 31 > >>> 0701x36-66.7.1.1 > >>> 30 37 00 20 20 20 20 20 20 7. > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses2 > >>> SCSI INQUIRY failed on ses2, res=-1 > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses3 > >>> SCSI INQUIRY failed on ses3, res=-1 > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses4 > >>> 00 0d 00 05 02 33 00 40 02 4c 53 49 20 20 20 20 20 ....3.@.LSI > >>> 10 53 41 53 33 78 32 38 20 20 20 20 20 20 20 20 20 SAS3x28 > >>> 20 30 37 30 31 78 32 38 2d 36 36 2e 37 2e 31 2e 31 > >>> 0701x28-66.7.1.1 > >>> 30 37 00 20 20 20 20 20 20 7. > >>> [root@ZFS-AF ~]# sg_inq --hex --len=64 ses5 > >>> 00 0d 00 05 02 33 00 40 02 4c 53 49 20 20 20 20 20 ....3.@.LSI > >>> 10 53 41 53 33 78 34 38 20 20 20 20 20 20 20 20 20 SAS3x48 > >>> 20 30 37 30 31 78 34 38 2d 36 36 2e 37 2e 31 2e 31 > >>> 0701x48-66.7.1.1 > >>> 30 37 00 20 20 20 20 20 20 7. > >>> [root@ZFS-AF ~]# > >>> > >>> > >>> And here's dmesg after fresh reboot: > >> > >> Well, that's weird. Your firmware versions look OK, though you might > >> want to upgrade mpr0 just to be consistent. The next thing I would > >> check, if I were you, would be devctl messages. Edit /etc/syslog.conf > >> and change devd's loglevel to INFO, then HUP syslogd. Now every > >> devctl message should get logged in /var/log/devd.log. That will tell > >> you more precisely than dmesg whether there are any arrival or > >> departure events. > >> > >> -Alan > > > > Huh, I never noticed the 6 vs. 8; curiously, mpr0 and mpr1 are the two > > connected to the front expander... and where I've never seen an issue. > Tho > > perhaps I scrambled which cards are serving was which in my testing - I > also > > moved mpr2 to sit on the other CPU's PCI bus. > > > > I've added the devd log, although I haven't been able to trigger the > event > > yet anyway. > > Tried to assert hw.mpr.2.debug_level, however it seems like hw.mpr > doesn't > > exist. > > hw.mpr.debug_level is a tunable which, if set at boot time, will > affect all mpr cards. What you want is dev.mpr.2.debug_level, a > runtime-controllabel sysctl. > > > > > Finally, I haven't the slightest clue how to update the firmware; the > Avago > > site only has a product brochure for the 3008 anyway :( > > It's fairly annoying. First, you must figure out which card you have. > 3008 is the name of your chip. Your card is probably a 9300-9i. If > so, go to this URL and click on firmware. If you download > "Installer_P10_for_UEFI" then you can install it through the EFI > shell. But they also have an installer that runs in FreeBSD. To use > that, download both "Installer_P10_for_FreeBSD" AND > "Installer_P10_for_MSDOS_and_Windows". Unzip the latter and extract > the .bin file. Then unzip the former and run the executable contained > within, providing the path to the .bin file obtained from the latter. > You'll need a reboot afterwards. > > > http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9300-8i#downloads > > -Alan > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@freebsd.org Sun Dec 13 08:30:18 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA445A3B98F for ; Sun, 13 Dec 2015 08:30:18 +0000 (UTC) (envelope-from sagig@dev.mellanox.co.il) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49A161E85 for ; Sun, 13 Dec 2015 08:30:18 +0000 (UTC) (envelope-from sagig@dev.mellanox.co.il) Received: by mail-wm0-x22e.google.com with SMTP id p66so24258675wmp.1 for ; Sun, 13 Dec 2015 00:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dev-mellanox-co-il.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=L6lUa5lLscCY1V5JBUwG4KyTzNwYRM1UtLc6jmpfoA0=; b=xYYmmKP55U7RyPESC8d8LoMi2JFUex1h1LK6iOVjxzvhw3aBDYWpru/Jw8jftDlOco NZLkuWqHYPWY2Tq+2DOLvjV6ZJs0d4lOqBZRet3/np5EbZQrggL/LbCPd0GrpuFPLqqm XX9JOs1dt73OR6W35hbHXpmz1kvlN9HUTh6PsYn3wGEfvFr8DcOueI8Eov/waaFqNFl2 HKb0UbEpoCOsuexGAhv4uGE1sYXEi9CUbvdSkQtot2/He9BgQ0I/oFpAGdPcLip2TGts aljIy8W1Z88+qv2ERRrccI/OqMZCYipbs+yrh2VNwM7JQWrlSke7AXz0+c5QrFSfu5UZ R3eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=L6lUa5lLscCY1V5JBUwG4KyTzNwYRM1UtLc6jmpfoA0=; b=SBlJjjgd27FwbtjwxXVYisnGUxylpf3ep771fQHAM+BTy8JYZEAwKOPGLV+ijYep2m 6OSgNk8UcH1mi/kn/1udjxIv/dPxJrkV2UB5EUn4h7NKZBUr2IJI/v4DpTZ9EWbUkZ2r zdeKP7zisnTYd1zy4I5oksmjj1xbNHyejaEL7h5LtwT38Bsqo/AHAXd8hl6lHG/abDDM PxEevgKM9aKQD7/aXCCEljwnYmSVzF/0W1UNe1vq+My/krG/CJaGYTGk3pojgMxG7ubY 1UlOSFWuIpeFhLrUCpQmGKJHOrIypS+BCSLPjiE95ECPVtXBXCCEdUS5W4PYFzqbNiCQ hWRg== X-Gm-Message-State: ALoCoQkgsEDxJntelP5zOA6VxgUHADPG78CmSJspLFB6wDeSi0psCBUaJgSsLpvdkrkix4XsBDqk2qSQAVdn717bPnO2AEBdeQ== X-Received: by 10.28.144.139 with SMTP id s133mr17398182wmd.90.1449995416432; Sun, 13 Dec 2015 00:30:16 -0800 (PST) Received: from [10.223.3.75] ([193.47.165.251]) by smtp.gmail.com with ESMTPSA id kb5sm24329523wjc.20.2015.12.13.00.30.14 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Dec 2015 00:30:15 -0800 (PST) Subject: Re: splitting iovecs to bios To: Konstantin Belousov , Max Gurtovoy References: <56696E03.8050202@mellanox.com> <20151210150210.GY82577@kib.kiev.ua> Cc: Sagi Grimberg , freebsd-scsi@freebsd.org, Hans Petter Selasky , Oren Duer , freebsd-geom@freebsd.org From: Sagi Grimberg Message-ID: <566D2C91.9050900@dev.mellanox.co.il> Date: Sun, 13 Dec 2015 10:30:09 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20151210150210.GY82577@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2015 08:30:18 -0000 Hi Konstantin, > There might be indeed a reason, it could be that some drivers expect > blocking to be done by the userspace. The drivers could have some > restrictions on transfer sizes and atomicity of transfer, which would > be broken by the unconditional merge. I cannot give you an example > of such driver, known block-aware drivers like sa(4) only require the > bio size to be multiple of the basic block size. I'm surprised to learn that the generic access layer splits IO requests just because some block drivers cannot handle it. I'd expect that this sort of limitation would be communicated by the drivers in the form of device flag SI_NOMERGE. > OTOH, I see no issue with adding a SI_PHYSIOMERGE flag and doing the > merges for the driver in physio(), when unmapped request has consequtive > iov elements ending and starting at the page boundary. I'd say it should be the other way around, physio would always strive to append/merge iov elements but wouldn't in case the device does not support it. Moreover, some modern devices does not even require the page boundary alignment you mentioned. These devices can execute IO to/from any arbitrary scatter list of buffers. From owner-freebsd-scsi@freebsd.org Tue Dec 15 04:40:41 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3371EA43A0A for ; Tue, 15 Dec 2015 04:40:41 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1EC3D1D0E; Tue, 15 Dec 2015 04:40:41 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from [172.17.133.77] (dip-cali.panasas.com [64.80.217.3]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0NZD00MZ7RJS2M10@mr11p00im-asmtp003.me.com>; Tue, 15 Dec 2015 03:40:41 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-12-15_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1512150068 User-Agent: Microsoft-MacOutlook/0.0.0.151105 Date: Mon, 14 Dec 2015 19:40:39 -0800 Subject: Re: Accessing static drive info w/o ATA identify and lockup with camcontrol identify From: Ravi Pokala Sender: "Pokala, Ravi" To: Kevin Bowling Cc: "freebsd-scsi@freebsd.org" , Sean Bruno Message-id: Thread-topic: Accessing static drive info w/o ATA identify and lockup with camcontrol identify References: <80BB5907-CC31-4F06-9C70-E6F7834FF28E@panasas.com> In-reply-to: MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2015 04:40:41 -0000 Does anyone have any thoughts about this? If not, then I'll code up a patch and throw it on Phabricator. -Ravi -----Original Message----- From: Ravi Pokala Date: 2015-12-10, Thursday at 08:10 To: Kevin Bowling , Ravi Pokala Cc: "freebsd-scsi@freebsd.org" , Sean Bruno Subject: Re: Accessing static drive info w/o ATA identify and lockup with camcontrol identify >-----Original Message----- > >From: Kevin Bowling >Date: 2015-12-10, Thursday at 04:58 >To: Ravi Pokala >Cc: "freebsd-scsi@freebsd.org" , Sean Bruno >Subject: Re: Accessing static drive info w/o ATA identify and lockup with camcontrol identify > >>Thanks Ravi! >> >>Rotation rate is probably the most important thing and thankfully easy as you suggested: >> >>https://reviews.freebsd.org/D4483. Would be nice to land that in 10.3 so I can swap the SaltStack module over to it. > >As I just commented there, I was actually going to look at this this weekend. My concern is that the d_rotation_rate does not strictly map to the actual rotation rate - there are some special cases and reserved values. I was thinking something more like this: > > sbuf_printf(sb, "%s", indent); > if (dp->d_rotatation_rate == 0) > sbuf_printf(sb, "unknown"); > else if (dp->d_rotation_rate == 1) > sbuf_printf(sb, "0"); > else if ((dp->d_rotation_rate >= 0x041) && (dp->d_rotation_rate <= 0xfffe)) > sbuf_printf(sb, "%u", dp->d_rotation_rate); > else > sbuf_printf(sb, "invalid"); > sbuf_printf(sb, "\n"); > > >That would be more accurate, but slightly harder to parse (depending on what's parsing the XML). I don't have a strong feeling about this; what do other people think? Should it just return the value provided by the drive, or should it do some interpretation? > >>Next in priority would be getting firmware version.. >> >>In 'camcontrol identify' it looks like: 'firmware revision DXM9203Q' >> >>In 'camcontrol inquiry' it's part of the device string like: 'pass0: ACS-2 ATA SATA 3.x device' >> >>Do you have any suggestions for wiring that into geom disk? > >Interesting. I never noticed that firmware wasn't already included in "struct disk", like drive model and serial number already are. It should be trivial to add, but keeping a copy of the string will of course make "struct disk" larger. That might have implications on KBI compatibility for out-of-tree drivers...? Again, I'm not sure. > > >>And lastly, yes bus speeds would be nice (especially to spot hard/soft misconfiguration). It shows up like 'protocol ATA/ATAPI-9 SATA 3.x' in camcontrol identify and can be seen in the inquiry string above too. Do you have design suggestions on that? > >I'm sure the string that's generated by CAM at attach-time could be preserved. Again, there's the memory and KBI issues of adding another string to "struct disk". > >-Ravi From owner-freebsd-scsi@freebsd.org Tue Dec 15 08:49:09 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEDA2A44E24 for ; Tue, 15 Dec 2015 08:49:08 +0000 (UTC) (envelope-from honzhan@microsoft.com) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0124.outbound.protection.outlook.com [65.55.169.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 718F819CD for ; Tue, 15 Dec 2015 08:49:05 +0000 (UTC) (envelope-from honzhan@microsoft.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=OVV2s29Y7+9/RbgY8wHmELTXju3loqrTnXM0bYG+ZTs=; b=Xp+c9+iOsVjx5xX8qyLDDGw90rWS4lZlF1zZn4mDnRcJy2V63ShZWjBt+v06JKLc0l+cNKZPXhIcj3FA/lTu5T78gbjVhdX2/pqI2Jbjy5Y95lk7/Mj/fTa6fIrG+mZOTS5YKEHpThVSudTpdkiJf/3DSF5qNjDT8rdC8ay4guw= Received: from BN3PR0301CA0053.namprd03.prod.outlook.com (10.160.152.149) by CY1PR0301MB0729.namprd03.prod.outlook.com (10.160.159.147) with Microsoft SMTP Server (TLS) id 15.1.355.16; Tue, 15 Dec 2015 08:49:01 +0000 Received: from BL2FFO11FD007.protection.gbl (2a01:111:f400:7c09::103) by BN3PR0301CA0053.outlook.office365.com (2a01:111:e400:401e::21) with Microsoft SMTP Server (TLS) id 15.1.355.16 via Frontend Transport; Tue, 15 Dec 2015 08:49:01 +0000 Authentication-Results: spf=pass (sender IP is 206.191.228.180) smtp.mailfrom=microsoft.com; FreeBSD.org; dkim=none (message not signed) header.d=none;FreeBSD.org; dmarc=pass action=none header.from=microsoft.com; Received-SPF: Pass (protection.outlook.com: domain of microsoft.com designates 206.191.228.180 as permitted sender) receiver=protection.outlook.com; client-ip=206.191.228.180; helo=064-smtp-out.microsoft.com; Received: from 064-smtp-out.microsoft.com (206.191.228.180) by BL2FFO11FD007.mail.protection.outlook.com (10.173.161.3) with Microsoft SMTP Server (TLS) id 15.1.346.13 via Frontend Transport; Tue, 15 Dec 2015 08:48:58 +0000 Received: from SG2PR3002MB0106.064d.mgd.msft.net (141.251.56.18) by SG2PR3002MB0108.064d.mgd.msft.net (141.251.56.20) with Microsoft SMTP Server (TLS) id 15.1.355.11; Tue, 15 Dec 2015 08:48:56 +0000 Received: from SG2PR3002MB0106.064d.mgd.msft.net ([141.251.56.18]) by SG2PR3002MB0106.064d.mgd.msft.net ([141.251.56.18]) with mapi id 15.01.0355.012; Tue, 15 Dec 2015 08:48:56 +0000 From: Hongjiang Zhang To: "freebsd-scsi@FreeBSD.org" Subject: Is there a method which can tell a SCSI device is valid or not Thread-Topic: Is there a method which can tell a SCSI device is valid or not Thread-Index: AdE3Dv5x8e4lUIBMQImDkMTyzc/m1w== Date: Tue, 15 Dec 2015 08:48:56 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [141.251.57.4] MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD007; 1:gqeSpM3WXJL3bORwHJAVw2BUN6ILR9bA1bhGaDnk24LUf+OYQI9X6LpxXC9mz514a4o8L3wKJyZcUpAYGDSzdC6pu0a5EvMmjSPgLq8M6eOj/xKvCQO1wIExFxmL7WhDG+kwM+QvnVUxabINrgzrJPAUzXBbd9kTqONfR1fhJ/0wvpPr0QM+J9u/E2qHMh47tNQ8PxPhdaCLVDxME4kXifAu56TEOmc10yKTYS+Coerxnu2Ajl0euimMpdk6oSbgUylk9ux1K1g+i27e/Wai9p/sNPCMFSZH0y5wxtqMzYzS8H/9hlk+nnTWCGV0eQAvoc8SOauNtLJyBMTd3TbWnbP2khoWOVbJd1tlRjCQEV8= X-Forefront-Antispam-Report: CIP:206.191.228.180; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(438002)(199003)(189002)(450100001)(15975445007)(107886002)(16236675004)(69596002)(19625215002)(2351001)(92566002)(97736004)(512954002)(19300405004)(189998001)(66066001)(81156007)(19580395003)(229853001)(5001960100002)(16796002)(790700001)(5008740100001)(10090500001)(2501003)(11100500001)(5003600100002)(1096002)(102836003)(2900100001)(84326002)(6116002)(110136002)(54356999)(33646002)(86612001)(5005710100001)(108616004)(10290500002)(50986999)(3846002)(5004730100002)(300700001)(87936001)(260700001)(86146001)(10400500002)(1220700001)(86362001)(24736003)(106466001)(6806005)(586003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB0729; H:064-smtp-out.microsoft.com; FPR:; SPF:Pass; PTR:ErrorRetry; A:1; MX:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0729; 2:9Q7UVbm2K4hgqXodu14J3g0heo22+MJu49yOeXnav2a8FgpmqXhFDH6159t81BxzBNJhV+VbSpltxSckwdWLyLReQDrFdBdaWOVo0W4nDzs8hSbK9+b9PdrL5MZ8mlsWC8leL4YG0r6udWTiErx6fg==; 3:PtunfPAH4ElOGFxvHrpFIWUTEseI1PduCrQJbBrWz7Y7R/Ps76PpL732TCWy/x+hzj13Xwt5JKASJzeSDizlc1ezlMaRuaq5Mxtp6Lw/sJsxl3Rmht9jSpfhkjTdf2uIzibAZska5uGKva7oYPXqf2lUChiy6bHUwAvK1TVsi5h7w7XyFZMFo/uviJr8COGCArbxFjuQiwOq2AjArrxAKFZbHc3N3W2Gz8L2v6E9omBm1EXnGgnv4zV5JPxuVvAMwnObY69l5qtiUvnyg42Tgw==; 25:wTCtAr7H9xxJtphkCcZwuBphO4Xb/1xQMYaLCvlDMXIPkdDZLpzbTpLFIjwpgz0VScd+PmRqdhBKncqNQkOYZTnBENmqGNmakwg6PwRtareObFd/oC0YvNrM2TYipqC5kd4rtV7SaQdgY34su24IDg89DyPyctbBiHHKWknnW91gbGWC1lr6ynBCnP/ADIS0fptD1uVnSAQFZCvbQB1u+OJRueo4gP3FZWT8Et1rICXGiojeKDzzCrOqLkjtVr4SD0D3IlywXBDjdV+OYE5K+g== X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(8251501001); SRVR:CY1PR0301MB0729; X-O365EOP-Header: O365_EOP: AllowList from IP - set SCL to -1 X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0729; 20:kjWnzLK3vtrh8Yr0z1SAPeq35faF7jsMIFCFooCtEKFEhjannbRB6XvVFB0+H9Xskq9rgYce8bOXFXPOSyYs2MM7C0oKKNrawQEA8RKiRy7MC5uhSa087AE4ylMcBbEGPOPVvJinoLWFrQOiS/z2N2lmaKdo38dldiaA+1hipWP6zfNbNhQ6tnbLGxhUXhgOWzwkewtN1a7HfSeefi1WjZAIXhP8zVpd/iBzUnNA+ZDQDs4s2l5k0vzYV27VYBjd+xg1NEQWYrsuficrOT2ZFWjjE0mv9A+W4XP3oFZUAzaCU97H5ugtQqBJAfM5xmvj2D8ZP7vXEqMQH774ZYnAAkBJ96sB5MW6BXZWd1bAsp+OXUU5AniIyooSHpRwmHXNUoNwmSDhn9wlxTJm8+e2fS4D8mjgvCET7znhHlmcXdEsn26Hl5eQOLX5qSUBSuBXJjyjytHqJgrSAFEngCcPp5EOtkPiusrTHTjn4nSvyNDE24xbu3JBXKQ6x9UAn892UtS/5UZ7l76NW4hnY7zzcIMLrbkHtZ/eREwKKowV/i3nWAIoDrAQyBJDuxz37Vn+KSCFI93PcITAQnURwChOIwgcCuy8cA9oM95VcPzGk8o= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(520078)(5005006)(10201501046)(3002001)(61426038)(61427038); SRVR:CY1PR0301MB0729; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB0729; X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0729; 4:o8v6z+k+hNpNiD0+cP4xhsu6OPY8bHrmEOrMPs9dUeM3Dr3itMX6IoYEWGAKcL8gP7IJ9rm3Zo7a4L/tc26nixZS8YV8hm39PiEiTWR09cGKfuamWX8siWAtUZYhViyGdYOUP9fcIDjuu6v7frrfO6oBM92K62UPWgzNGRIBP3S8VP5lHJMcbEbcbzEop5B90ME25wVi2SUHwvkPunyXkr1DPEx988luS1ebLQfflyC8qfsqxd2bPFCW5KhkbjYBXAjCvVGY6KNjd80L0SPyKoUkqPkti4aObCY+Lmb2ssW+kAllTc7MuPGSDdqEA1dNBFAlK+bevtsE+zwEhadTJFXdOmT6znrIyvX927Qe+yMdngm2l3b75cfPo8GYQXKwIK7PDnh/s+skXhF4LjlrPbnkMsdkPfLM6kXda5Xfd242KCAiJ4QpPy1KR7cLhEJ8 X-Forefront-PRVS: 07915F544A X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR0301MB0729; 23:hsDGd2c2qwvD0Gf+BJChrHCOsoRLJG85uTP8eht?= =?us-ascii?Q?g5/E6u7o7GuVgI/FbxgDK42LKIMoyEyvEM2y1/gugVh9RFTEf3MyEf/RND+C?= =?us-ascii?Q?adSZo8UUs1/pUhLvgKl48AGZ3Uc6eXC3m31vgXvoIu6xpVoOYiBmAcB9ShZp?= =?us-ascii?Q?f610ANFNiv1mXw0n2ZT0psZHh7j0JQLXgjZ1Q/Ih9AEk6jbjlVcezDz/EJ5N?= =?us-ascii?Q?7zrZqsQ3QTvTWbrjlP2B+indk+P970Q+s8YYOWLxRLciZXvwzzcbuzy6boJC?= =?us-ascii?Q?bAdN2KXxgrm9YbNlTAXvbyYmIPEo1UEc31MXl1mtq3mPiNt6DxgS31hsEdkU?= =?us-ascii?Q?Tde0mIVM85BGR0GkOkroPC0cY2OffM/YRg3OMhL+di5CYEBpq7724akWlRa7?= =?us-ascii?Q?KhCMX2CjLq44weWAfZYWCnoCPJ/4zjN0jYsqD0ZhrwTBwGKQQFsy8iDs8jjo?= =?us-ascii?Q?NxYpEw914tdWYJ7M28YqPy+UYvlTfIN8QsdzymDw1kZ2YEo5BYEUzQj0/07A?= =?us-ascii?Q?GWHRcu+BLqESksP51sqdap9ZPrWWb68a4LeCQQOkhh6Ccp++EXez57eNsLUI?= =?us-ascii?Q?l/cnbUdyhemfYuUDOi8ohvtfRtUFEkCCtrwYomVla66LOaW6UBiTYdB/1pwY?= =?us-ascii?Q?6L3massRFV/qZSPfCCdo4pPz53HbHjeJjLVPghzHgxAFu3AQsL/K839ilrTF?= =?us-ascii?Q?mq+suAG8Z/O9jXhiGZvIccsEjYc1uhqeCOZrKCp9Vmg3kW08vfmHpXOPUmeq?= =?us-ascii?Q?catXJpRSgifA3r4FMw6wWiax5NS7vuGV57WzhIvM3VyDSnafergqnimkD2Gw?= =?us-ascii?Q?ojliI4eoblsArup3nJrQQcfdSfl53oLpeiTrlcoZ8M8SQEOavqVV4bugUx6m?= =?us-ascii?Q?1bQEuwJMkBhLnWeTXTmC04K6SgNTGTmEH6CqpKHIKP5tQ+blw5LHnVEp1qP5?= =?us-ascii?Q?164MvRn16t+ObDpQUZelBerHNDHaxXt4AxIlZA6+cWf+KEDz1cmpetmT0E2D?= =?us-ascii?Q?/VIBFH7sbkHK8BbUkPDEfMaEHK/P3G1muu5lWVXok7rzR2ZRaxouxGZz+NUC?= =?us-ascii?Q?mwoKkbUeTkalFotfpHuZB8RD9dX0YymAqS0MmlaQUvbOcFJ7Cxw0OacGUf3j?= =?us-ascii?Q?HTG8MMhiS7lSusjMQpqlNaMjbtOyo7REGuuHnmkcbx4NT9LX+Midjs/9MNAh?= =?us-ascii?Q?xEoAbHpFWaumpCP5z1H441JMSmjJ1F5iSNU8JRquN1dhJMS5zX0YsSMXVj7D?= =?us-ascii?Q?gIT5J/vStK/UmSlqNa5S4VChMNVgT7J93s8fID+ASlmaYnZ2u4lMmP0GScmG?= =?us-ascii?Q?0mjKcPAH5MXEBKbdVV2zZxM6FJ0Bwc/6bWeSnc9NM8G+dXrKvTvD8gachkCD?= =?us-ascii?Q?Z55tnQiDJSUbxb2fvkCte3BpftSaAhfzuaX4wHPc8QSeFdivZngW1DaPGa7H?= =?us-ascii?Q?aha0jnO3pBwIInz/qj/VwZhFO/cgXGV8=3D?= X-Microsoft-Exchange-Diagnostics: 1; CY1PR0301MB0729; 5:gUQOobpQoCRxjb3XbxjzPCBdYhvlYyqi47FCXhf7aMFtQC/XYW1pgb7Lif04ChIY0Bi9G3SmfgxWJOwqa9boATeKduhbbtvhVC+XtcCh5Xc9W05Mw6DIZ9cKy4TzA/+MtELa4FRAZ8di+SnmNEH7cw==; 24:izW8uYc0nEwIhcjHksn73zbSrWnvujjCa8JPJ8cz+yNvOkaSxxBDQF9czA23iPxW4+O0+g+m3TR3iV1zwCXheR7NaFAryjT5BVMBzavIHz8= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 15 Dec 2015 08:48:58.9709 (UTC) X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[206.191.228.180]; Helo=[064-smtp-out.microsoft.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB0729 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2015 08:49:09 -0000 I'd like to know whether there is a utility method which can tell a scsi de= vice is perfectly installed or not. Is there a method like "is_scsi_install= ed(struct scsi_inquiry_data *)"? Background: When I developed storage drivers for hyper-v on windows 10, I found in the = windows host tells VM some of the devices status are ok, but in fact such d= evice did not have valid information. For example, "Fixed Uninstalled SPC-3 SCSI device (LUN not supported)" if I= print its inq_data. The following code is used to print the inquire data: struct scsi_inquiry_data *inq_data =3D &(ccb->ccb_h.path->device->inq_data)= ; scsi_print_inquiry(inq_data); The log I collected: Dec 15 11:19:33 honzhan-dev2 kernel: Fixed Uninstal= led SPC-3 SCSI device (LUN not supported) Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS **SCSI_STATUS_OK with = invalid SCSI Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS 18: hv_storvsc_on_ioco= mpletion type=3D0x1f, SPC-3 target=3D1, lun=3D0 Dec 15 11:19:33 honzhan-dev2 kernel: Fixed Uninstal= led SPC-3 SCSI device (LUN not supported) Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS **SCSI_STATUS_OK with = invalid SCSI Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS create_storvsc_request= probe:0 storvsc:1:0 0:0 Dec 15 11:19:33 honzhan-dev2 kernel: Fixed Uninstal= led SPC-3 SCSI device (LUN not supported) Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS XPT_SCSI_IO device->lu= n_id=3Dffffffff Dec 15 11:19:33 honzhan-dev2 kernel: HV_DEBUG: VMBUS create_storvsc_request= probe:1 storvsc:1:0 1:0 Dec 15 11:19:33 honzhan-dev2 kernel: Fixed Uninstal= led SPC-3 SCSI device (LUN not supported) From owner-freebsd-scsi@freebsd.org Fri Dec 18 04:50:44 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7DF4A4B0FB for ; Fri, 18 Dec 2015 04:50:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9AD2F1A23 for ; Fri, 18 Dec 2015 04:50:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9A24DA4B0FA; Fri, 18 Dec 2015 04:50:44 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99C5CA4B0F9 for ; Fri, 18 Dec 2015 04:50:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6179F1A22 for ; Fri, 18 Dec 2015 04:50:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qg0-x229.google.com with SMTP id v36so24998493qgd.2 for ; Thu, 17 Dec 2015 20:50:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=TLSq9gfWleevEW7AxC3cymlJDeS97U5WGnUd2Uuz5xE=; b=w0HlXNGiPPKPxRrzlo0XaM2w/S439IyQND907ByC4Jf+6syGEe2Lx3W76FZdwzi5X3 xLY0qpadWF8uKEPl9DMonQ3F9Z/WvtvYwM7qQ6IebpAZ97EwugQmv6XufGNdxmKqdG8Q SPl54Za9cFUpAMGFf/ZCAGp7FBb7SjQGGFmL3McbJNqpnD4Kv9uMRQ7v3Wfsc+jW4sh2 18Wq3ciVesL1SyYKogtJ8m9RziNWgi7f4WnsanmvpXmhq6gjagWrawqsT0trSrr6OdBX wr4z1BdIz04us+A0GJWaRc5njqedCeTwDojJ5dfnIshwM0k1jZOZOi8zBtD0pNrkxQVG aFug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:content-type; bh=TLSq9gfWleevEW7AxC3cymlJDeS97U5WGnUd2Uuz5xE=; b=kQUQPvxEPGNeowhXN8Ec6AQLwuNQhs2ltB1qYXcQqxHzJb/QyF4DRurFW+Uy6yOA+v Y2fgzQlWrEaehMx1xQE3u+ec4onMjKquEnxrLMit3gRkInrIzKmaLCeADDrCybE4Ju6l P7QUBkR3VwsBFEfhzFxZYJ+vUvyDazcP4j/TvESykQLhdUi7xDWk9dfhLKW9XFwKhXn1 4WQWuuvTjo2TDcOMs6kFLWBjHWx8R//C5Q/xTan6wp3CiRu5DHa3/UnCapqCqqqnglXE pdmU5Gq8+qbAjtTmFS3c48kH0ZreK9kS4HTau01hxolu5Lo5F8Ucp/+oP2RBJi/Gy4Zw gGMQ== X-Gm-Message-State: ALoCoQmc+EV9OB530w6xmCCI0oYwZaQCeH8PaaybkGU3K1/yrUCcbOxgZ5X1hSXax3M4mEpY/SJCtmKh8z3TD8OpGtsSRF0kaA== MIME-Version: 1.0 X-Received: by 10.140.196.69 with SMTP id r66mr2304705qha.40.1450414242795; Thu, 17 Dec 2015 20:50:42 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.27.181 with HTTP; Thu, 17 Dec 2015 20:50:42 -0800 (PST) X-Originating-IP: [50.253.99.174] Date: Thu, 17 Dec 2015 21:50:42 -0700 X-Google-Sender-Auth: m8DIYgUPrHVUgPTny6gcdCuPKT0 Message-ID: Subject: New CAM I/O Scheduler From: Warner Losh To: scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2015 04:50:44 -0000 I've put up the I/O scheduler that I've been working on into phabricator for review. A number of items likely will peel off this review, since it also has the NCQ support and a few other things. https://reviews.freebsd.org/D4609 Please comment in the review. For background see http://people.freebsd.org/~imp/talks/bsd2015/iosched-v3.pdf Warner From owner-freebsd-scsi@freebsd.org Fri Dec 18 06:23:56 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43CE1A4ABC8 for ; Fri, 18 Dec 2015 06:23:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 247BA1DA7 for ; Fri, 18 Dec 2015 06:23:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 23F45A4ABC7; Fri, 18 Dec 2015 06:23:56 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B306A4ABC6 for ; Fri, 18 Dec 2015 06:23:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB5361DA6 for ; Fri, 18 Dec 2015 06:23:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qg0-x22b.google.com with SMTP id p88so10964632qge.1 for ; Thu, 17 Dec 2015 22:23:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=WRuULOCDIU1wgYov32r5i9i+NBFDgFqL0XDZ+iXcOvA=; b=fgXW3Jct/ZKahgbq5dN9r9AThFDw2X5xTONXrf/JX0BsUFv4pm5XrlzSh8A/Y2myuL MI9bGbVeWQ0VZU+im+dObsSJXod73BBsDPbdz85w0Vw6fHTwuXRVsCvaiXFKjRu0A2Nv 6Y6iqKrGady1aboXuEleNMzcg3Zq5BK3TcmWRCyzppdnsRgk1z1kfXm2vdRr3KT1lqal rUAdi/jf1PKKVv2PiCfsv+08Jl5KMUbpc0E1bT30YSknwPBpDn+Aam/wQWlAreKosOGK ZXuEBNatnVJJtmCDb1qrYH8sjszu2DPRm7KIqpI1jlAESnqvTWUHo9WlYUn0fb+jTWhM UuYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=WRuULOCDIU1wgYov32r5i9i+NBFDgFqL0XDZ+iXcOvA=; b=RmQDJl0boMwMgLXn7cSNB9ZFYXcEiGi87ZlwpOZhaY1MAbgiq9FuMoI2hXTk1bi1cY 7qe/fgCSOEpL+Nst9lg+zBylSm3uoYBptINyY5JgMVh+JwarWDR/MdgKunXBjur7Iz9B 9Z3woRwR4HjxQazSsp5juztQ0g1+7p5ehX+DJD7CKWHddNmHQUwnQvDiJ4kbKrgK9VC9 U0PLhT4bFlBK7cSLt55ATCRpb09L/M6iad3Q0WliLvkQaO7kEY4jzpJ5GNFY93204s9s eoef7viQaVacjJIpjySLGAVsJGFQwhJGTVJSEZ/Du2JxiHKh2+8d0lzDEOjShlAgs5bD fbiQ== X-Gm-Message-State: ALoCoQkrbiDVtnoZei+qxMVbEaBB4MAtnKZSzzy4Y6lF9b6LRUlL3VhpUc42Gze4pJQEGIaFQORxk0a5wZDfnI1IhFi17bZLvg== MIME-Version: 1.0 X-Received: by 10.140.29.131 with SMTP id b3mr2523375qgb.50.1450419834686; Thu, 17 Dec 2015 22:23:54 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.27.181 with HTTP; Thu, 17 Dec 2015 22:23:54 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: Date: Thu, 17 Dec 2015 23:23:54 -0700 X-Google-Sender-Auth: Vy8bfRxGo7y9-RwZEqVwRAA74Gw Message-ID: Subject: Re: New CAM I/O Scheduler From: Warner Losh To: scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2015 06:23:56 -0000 On Thu, Dec 17, 2015 at 9:50 PM, Warner Losh wrote: > I've put up the I/O scheduler that I've been working on into > phabricator for review. A number of items likely will peel > off this review, since it also has the NCQ support and a > few other things. > > https://reviews.freebsd.org/D4609 > > Please comment in the review. For background see > https://people.freebsd.org/~imp/talks/bsdcan2015/iosched-v3.pdf is the correct link. Warner