From owner-freebsd-current@freebsd.org Fri Apr 15 01:22:34 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 329B9AEC2F7 for ; Fri, 15 Apr 2016 01:22:34 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 26ED4183E for ; Fri, 15 Apr 2016 01:22:34 +0000 (UTC) (envelope-from bright@mu.org) Received: from AlfredMacbookAir.local (unknown [IPv6:2601:645:8003:a4d6:99ab:a16d:774e:d281]) by elvis.mu.org (Postfix) with ESMTPSA id BB342346DF92; Thu, 14 Apr 2016 18:22:26 -0700 (PDT) Subject: Re: Heads up To: freebsd-current@freebsd.org, Warner Losh References: From: Alfred Perlstein Message-ID: <57104251.5080102@mu.org> Date: Thu, 14 Apr 2016 18:22:25 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 01:22:34 -0000 On 4/14/16 3:42 PM, 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. > Yowch... With data at stake wouldn't a whitelist be better along with a tool for testing it? Example, you have whitelist and blacklist, if the device isn't on either list you output a kernel message and suggest they run a tool to "test" the controller and report back the findings? -Alfred