Received: by 10.223.185.116 with SMTP id b49csp7291283wrg; Thu, 1 Mar 2018 03:10:00 -0800 (PST) X-Google-Smtp-Source: AG47ELv/TAFVfl1IhrfnK0qCWnNb0MY97dJJ3GAkAIidRAoGOxsBTzIwxLxgwdug2HJHjv27sEPp X-Received: by 2002:a17:902:720b:: with SMTP id ba11-v6mr1629297plb.148.1519902600534; Thu, 01 Mar 2018 03:10:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519902600; cv=none; d=google.com; s=arc-20160816; b=iCnw6mx7Ou8tw4uqEFz/RjXSX97Y93MYRoFnwlUiOL74dgrcRZi8iKG//oUj9QT0xF bqSVs39Coz0tjzCL9A/w6LvBY8y4LdqIZQ90LYXksQOYQPlqeBdtPP01wcgek60ZLssa sugk9G67aJF05HVGGVzHIzoyD//vYnnRBlol3umnesLDCHlbwmqkwBnieRDwSmUrcQDj 8OKLsnUzYIC7TEgu6EFrNpp6/58wBAnbfXf0DnMtOmSQeqHKDT4oX8QNSaKZ8GsHH00U LINDDZJBQk+EtJnzHpPfA3jrKgcKIAnpw9kEUh94JynAu2612fDejfZc9A9wLcriZo4v iT3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=JOeXvRh08rHzVaG0DRXCdYky28JkklpyUM8l2HteuKM=; b=BhkPDLzPfCDWUAS6PrO9fRKLSYf2ovFxdw1VNVAjTVJAKg0nsGgLq+AdR0HVgUHXnG 1Jh6GBNrb3qkY9e+GUecKXJoUsiOOcaf7XLsuW7NA05TWCORTy7gBA1VNJ3CUEdHcfQb XAIH3TffP+oXboGyL11GpUdQJ0UJVsumw3uX2aL3nd7t3T7l5LiaYzQYrnU8f/Rx4BAS nncN2a9bfFzmX+7Byo/B9ujJfbb+RUfJPZ2QlJWnb7JxENpz0jXx8HQv1nqPXMI15LOj JqJ1jNssIgoKqfk27rLd1nwz8eQWOx0vVTam/WHnjlXk0lxRAKnJ0/6PhSabOQ0X3Wex 3uKg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f4-v6si2874348plt.765.2018.03.01.03.09.45; Thu, 01 Mar 2018 03:10:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967709AbeCALHs (ORCPT + 99 others); Thu, 1 Mar 2018 06:07:48 -0500 Received: from mail-wm0-f48.google.com ([74.125.82.48]:38510 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966703AbeCALHp (ORCPT ); Thu, 1 Mar 2018 06:07:45 -0500 Received: by mail-wm0-f48.google.com with SMTP id z9so10768895wmb.3; Thu, 01 Mar 2018 03:07:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JOeXvRh08rHzVaG0DRXCdYky28JkklpyUM8l2HteuKM=; b=lK/LI3Ib/KfOq0n6oc/fNxWX+L7N8WVf8lBK0mrBhrgBG9rUOyLHBCncFuj/W3hEwY itYmVu3icyGby9bst7s8Z/5fC7xPUaaeq2mNbmxEb+IrnweBOf9j6xfv0H+8/uRZAbIX L/kRFkcLfsRNNtX845EYLaUxuM4yWKHNORCpPZ8JtPskjGl0rXzklNTbIstzUdmX+pz0 qF4WQclreIWGmXOFMIPJn14PgbXP7VUeIyUfE/FbPeqccgmDEdTuNggucX6fLHY/9MFh 5MzLdy82N/+iJ2R+bmRc5f+nyeSKzUcxfG7HiwRh0hgvY9WOGe/Cs/u0wS2jFNRIMgji OhSg== X-Gm-Message-State: APf1xPDvU4jIScyqoX7OZS/u6RLkztiyyQs69rMFSZ8KiD6u9uOqnmV9 831DrmfaMHYl6nHVS/4WrVw= X-Received: by 10.80.177.86 with SMTP id l22mr2382995edd.88.1519902464428; Thu, 01 Mar 2018 03:07:44 -0800 (PST) Received: from [192.168.64.110] (bzq-219-42-90.isdn.bezeqint.net. [62.219.42.90]) by smtp.gmail.com with ESMTPSA id y8sm3859546edk.43.2018.03.01.03.07.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Mar 2018 03:07:43 -0800 (PST) Subject: Re: [PATCH v2 08/10] nvme-pci: Add support for P2P memory in requests To: Logan Gunthorpe , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org, linux-nvdimm@lists.01.org, linux-block@vger.kernel.org Cc: Stephen Bates , Christoph Hellwig , Jens Axboe , Keith Busch , Bjorn Helgaas , Jason Gunthorpe , Max Gurtovoy , Dan Williams , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , Benjamin Herrenschmidt , Alex Williamson References: <20180228234006.21093-1-logang@deltatee.com> <20180228234006.21093-9-logang@deltatee.com> From: Sagi Grimberg Message-ID: Date: Thu, 1 Mar 2018 13:07:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180228234006.21093-9-logang@deltatee.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > For P2P requests we must use the pci_p2pmem_[un]map_sg() functions > instead of the dma_map_sg functions. > > With that, we can then indicate PCI_P2P support in the request queue. > For this, we create an NVME_F_PCI_P2P flag which tells the core to > set QUEUE_FLAG_PCI_P2P in the request queue. This looks fine to me, Reviewed-by: Sagi Grimberg Any plans adding the capability to nvme-rdma? Should be straight-forward... In theory, the use-case would be rdma backend fabric behind. Shouldn't be hard to test either...