From owner-freebsd-current@freebsd.org Fri Apr 15 03:56:25 2016 Return-Path: Delivered-To: freebsd-current@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 A5A2AAED865 for ; Fri, 15 Apr 2016 03:56:25 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7501D1431 for ; Fri, 15 Apr 2016 03:56:25 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3F3uMQc012666 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Apr 2016 21:56:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3F3uMei012663; Thu, 14 Apr 2016 21:56:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 14 Apr 2016 21:56:22 -0600 (MDT) From: Warren Block To: Warner Losh cc: FreeBSD Current Subject: Re: Heads up In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Thu, 14 Apr 2016 21:56:22 -0600 (MDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2016 03:56:25 -0000 On Thu, 14 Apr 2016, Warner Losh wrote: > The CAM I/O scheduler has been committed to current. This work is described > in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the > default scheduler doesn't change the default (old) behavior. > > One possible issue, however, is that it also enables NCQ Trims on ada SSDs. > There are a few rogue drives that claim support for this feature, but > actually implement data corrupt instead of queued trims. The list of known > rogues is believed to be complete, but some caution is in order. Is the list of drives queryable? Is there an easy way to tell if the currently-connected drives are on the list?