From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933052AbcFGVCP (ORCPT ); Tue, 7 Jun 2016 17:02:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56304 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932941AbcFGVCL (ORCPT ); Tue, 7 Jun 2016 17:02:11 -0400 Subject: Re: NVMe over Fabrics target implementation To: "Nicholas A. Bellinger" , Christoph Hellwig References: <1465248177-17970-1-git-send-email-hch@lst.de> <1465280632.5365.58.camel@haakon3.risingtidesystems.com> Cc: axboe@kernel.dk, keith.busch@intel.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, target-devel , linux-scsi From: Andy Grover Organization: Red Hat Message-ID: <9352d5f2-b75f-9cc6-9a93-2e49c0883e84@redhat.com> Date: Tue, 7 Jun 2016 14:02:09 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <1465280632.5365.58.camel@haakon3.risingtidesystems.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 07 Jun 2016 21:02:10 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/06/2016 11:23 PM, Nicholas A. Bellinger wrote: > Hi HCH & Co, > > On Mon, 2016-06-06 at 23:22 +0200, Christoph Hellwig wrote: >> This patch set adds a generic NVMe over Fabrics target. The >> implementation conforms to the NVMe 1.2b specification (which >> includes Fabrics) and provides the NVMe over Fabrics access >> to Linux block devices. >> > > Thanks for all of the development work by the fabric_linux_driver team > (HCH, Sagi, Ming, James F., James S., and Dave M.) over the last year. > > Very excited to see this code get a public release now that NVMf > specification is out. Now that it's in the wild, it's a good > opportunity to discuss some of the more interesting implementation > details, beyond the new NVMf wire-protocol itself. I'm sorry but I missed it, can you repeat the link to the NVMe spec(s)? Thanks -- Andy