From owner-freebsd-hackers@freebsd.org Wed Jan 4 15:59:09 2017 Return-Path: Delivered-To: freebsd-hackers@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 995A9C9FF32 for ; Wed, 4 Jan 2017 15:59:09 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F5211BA4 for ; Wed, 4 Jan 2017 15:59:09 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp002.me.com by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OJ900D00IQWYH00@mr11p00im-asmtp002.me.com> for freebsd-hackers@freebsd.org; Wed, 04 Jan 2017 15:58:51 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=4d515a; t=1483545531; bh=Kf2L7IBfAuGMbIul5UP8y9nZwq1Fe93JMEGbFRG1q6g=; h=Date:Subject:From:To:Message-id:MIME-version:Content-type; b=npJkCeQvh9llP6SpdKGGSKrbZgtmP3lMta/BeVfMiF7BovReUfNzJiTPoYzsB7gPJ cAatfLTXoph5aGY5X4Z5zGj7909bEE4S0lSKlhYJQz5x1AiM31ICt6//s7g5mOcUVv t5peh9f/ECrFRaym4OkP90rdvYqB9R6ixr5PNVUOx5XLlKbPhpNCjbu5MBA1OP7VL1 8WuglZG8jsN/A2ZiU3+pmseht1rRw6YDUgN/E+6H588yduq+K9XfNF5oYzo0h6UWEV 1BYxGx92Os6sJxNBwscbX2jU2mGIhxk2r6uhMvJmf+x+DOYDo/3hbl8iQtvmLkNqdR GqWcfiv+gcNDw== Received: from [192.168.1.4] (c-67-188-225-23.hsd1.ca.comcast.net [67.188.225.23]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OJ900JU1J20BT00@mr11p00im-asmtp002.me.com> for freebsd-hackers@freebsd.org; Wed, 04 Jan 2017 15:58:49 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-04_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1701040254 User-Agent: Microsoft-MacOutlook/f.1d.0.161209 Date: Wed, 04 Jan 2017 07:58:47 -0800 Subject: Re: New Kaby-Lake NUCs: Thunderbolt 3 and Optane NVRAM in -CURRENT? From: Ravi Pokala Sender: "Pokala, Ravi" To: "freebsd-hackers@freebsd.org" Message-id: <186F7B06-9EDD-4C92-99C9-0BC292E7B511@panasas.com> Thread-topic: New Kaby-Lake NUCs: Thunderbolt 3 and Optane NVRAM in -CURRENT? MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:59:09 -0000 > Date: Tue, 3 Jan 2017 20:10:00 -0800 > From: Murray Stokely > To: hackers@freebsd.org, Adrian Chadd > Subject: New Kaby-Lake NUCs: Thunderbolt 3 and Optane NVRAM in > -CURRENT? > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > I've had a good experience with the last generation of Intel NUCs on > -CURRENT and -STABLE. > > Today Intel announced their latest NUC offerings with Kaby Lake processors, > Thunderbolt 3, and their Octane NVMe SSDs. > > Any thoughts on how these will perform with -CURRENT? The hardware isn't > shipping yet, but will additional driver support be required to e.g. make > use of the Thunderbolt 3 ports? > > Will these use the Intel Wireless 8260 supported by the iwi driver? > > - Murray There shouldn't be any issues w/ the Optane NVMe SSDs, because they are just NVMe SSDs. The NVMe interface standard doesn't make any assumptions about the underlying media of the device, so you can have Optane-backed NVMe just like you have NAND-backed SATA or NAND-backed SAS. For that matter, you don't need Kaby Lake to use Optane NVMe SSDs, for that same reason. Using Optane *DIMMs*, *does* require some hardware platform support, which may or may not be in Kaby Lake; I don't remember the details on that. -Ravi (rpokala@)