Date: Thu, 14 Apr 2016 18:22:25 -0700 From: Alfred Perlstein <bright@mu.org> To: freebsd-current@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: Heads up Message-ID: <57104251.5080102@mu.org> In-Reply-To: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> References: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57104251.5080102>