From owner-freebsd-stable@freebsd.org  Tue Sep 13 07:06:04 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 BA93CBD7E99
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue, 13 Sep 2016 07:06:04 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com
 [195.16.150.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7C310D2
 for <freebsd-stable@freebsd.org>; Tue, 13 Sep 2016 07:06:03 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.36] (izaro.sarenet.es [192.148.167.11])
 by proxypop03.sare.net (Postfix) with ESMTPSA id EE77E9DDF74;
 Tue, 13 Sep 2016 08:58:56 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Intel NVMe troubles?
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <CAJP=Hc_1j7vnOSq7AUarqdMjRkLF-_vGBTXRLQrfsMcmjVL1nw@mail.gmail.com>
Date: Tue, 13 Sep 2016 08:58:56 +0200
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFC60822-0F21-4F4E-B28B-5F49B4A808EE@sarenet.es>
References: <CBC304D0-AA57-4EF5-A2DD-1888FB88DE12@sarenet.es>
 <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm+g@mail.gmail.com>
 <AAC8E93B-F263-4B7E-91DF-9EAC77FB2C3C@sarenet.es>
 <CAJP=Hc-3ogfoSZ0cjycm+sb0M80B6M5ZrGtWn1BjfOFPteGgdA@mail.gmail.com>
 <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es>
 <CAJP=Hc_dxM+gP9V2+n8OOwqLnOQxs+7zReG1xEAK=Jh=Y_BHRg@mail.gmail.com>
 <CAJP=Hc_1j7vnOSq7AUarqdMjRkLF-_vGBTXRLQrfsMcmjVL1nw@mail.gmail.com>
To: Jim Harris <jim.harris@gmail.com>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2016 07:06:04 -0000


> On 12 Sep 2016, at 17:23, Jim Harris <jim.harris@gmail.com> wrote:
>=20
> There is an updated DCT 3.0.2 at:  https://downloadcenter.intel.
> com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this
> issue.
>=20
> Borja has already downloaded this update and confirmed it looks good =
so
> far.  Posting the update and results here so it is archived on the =
STABLE
> mailing list.

Is it just my imagination or has trim performance improved dramatically? =
I=E2=80=99m being unable to replicate
the I/O stalls that I observed after running some simultaneous Bonnie++ =
benchmarks with large files.

Thanks,



Borja.