From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2870EC6FA82 for ; Fri, 23 Sep 2022 15:26:14 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C38008000F; Fri, 23 Sep 2022 11:26:13 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id BE81D80007; Fri, 23 Sep 2022 11:26:13 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AD7978000F; Fri, 23 Sep 2022 11:26:13 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id A0CEF80007 for ; Fri, 23 Sep 2022 11:26:13 -0400 (EDT) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 7A64A140742 for ; Fri, 23 Sep 2022 15:26:13 +0000 (UTC) X-FDA: 79943726226.02.2A9DED3 Received: from ale.deltatee.com (ale.deltatee.com [204.191.154.188]) by imf08.hostedemail.com (Postfix) with ESMTP id 51BB1160018 for ; Fri, 23 Sep 2022 15:26:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deltatee.com; s=20200525; h=Subject:In-Reply-To:From:References:Cc:To: MIME-Version:Date:Message-ID:content-disposition; bh=C81BnwO1LLn7rzdtw/smuBPO9/byip/ucPGw7WJmXyg=; b=EJgXMvWjdf974BGnhZ/H5B5xwv NXJvfp4f6oUfUKuWpK1vn1hJDJ0w7XSUyC8/69ObFbcR/PleMfld5liF8hFbsFBeRRknZIjUPWs3X yXCrUnVnYpYjPoX7DA9F2T28JKXXJEIV7eTiD4lUYvbR+CyKq571MvlRFoZLyNdx9mPjUl2mvtlUo 4fENvdIPwCyPgnqLNKCqyCRjsdhyoNHJAHPEzP7urRTm3wzaZDx02UPRrCfibr/1UFAwFMnP9bcfC s6eTzyHYgenOqLfahifc1Kx60xlysc8n5Vi/VtS1oTf1H5v275xPlJz5io+LMX8mSVIvh25GxjhUK dq0M7DHg==; Received: from s0106a84e3fe8c3f3.cg.shawcable.net ([24.64.144.200] helo=[192.168.0.10]) by ale.deltatee.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1obkYz-008uiH-2J; Fri, 23 Sep 2022 09:26:01 -0600 Message-ID: <47004362-15ec-5356-6c1e-ba69b1910cef@deltatee.com> Date: Fri, 23 Sep 2022 09:25:51 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Content-Language: en-CA To: Christoph Hellwig Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, linux-block@vger.kernel.org, linux-pci@vger.kernel.org, linux-mm@kvack.org, Greg Kroah-Hartman , Dan Williams , Jason Gunthorpe , =?UTF-8?Q?Christian_K=c3=b6nig?= , John Hubbard , Don Dutile , Matthew Wilcox , Daniel Vetter , Minturn Dave B , Jason Ekstrand , Dave Hansen , Xiong Jianxin , Bjorn Helgaas , Ira Weiny , Robin Murphy , Martin Oliveira , Chaitanya Kulkarni , Ralph Campbell , Stephen Bates References: <20220922163926.7077-1-logang@deltatee.com> <20220923060123.GA15698@lst.de> From: Logan Gunthorpe In-Reply-To: <20220923060123.GA15698@lst.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 24.64.144.200 X-SA-Exim-Rcpt-To: hch@lst.de, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, linux-block@vger.kernel.org, linux-pci@vger.kernel.org, linux-mm@kvack.org, gregkh@linuxfoundation.org, dan.j.williams@intel.com, jgg@ziepe.ca, christian.koenig@amd.com, jhubbard@nvidia.com, ddutile@redhat.com, willy@infradead.org, daniel.vetter@ffwll.ch, dave.b.minturn@intel.com, jason@jlekstrand.net, dave.hansen@linux.intel.com, jianxin.xiong@intel.com, helgaas@kernel.org, ira.weiny@intel.com, robin.murphy@arm.com, martin.oliveira@eideticom.com, ckulkarnilinux@gmail.com, rcampbell@nvidia.com, sbates@raithlin.com X-SA-Exim-Mail-From: logang@deltatee.com Subject: Re: [PATCH v10 0/8] Userspace P2PDMA with O_DIRECT NVMe devices X-SA-Exim-Version: 4.2.1 (built Sat, 13 Feb 2021 17:57:42 +0000) X-SA-Exim-Scanned: Yes (on ale.deltatee.com) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1663946772; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=C81BnwO1LLn7rzdtw/smuBPO9/byip/ucPGw7WJmXyg=; b=TWNzITls0eFghyKxIWPxiCYlmZTgoQ8PzXSQTHa8OTuu+i4prJd6oZ7O+pC7sX2mj5Mt2N z7hi+GbBy8sJ0qBsyGK9TNRd6mCnx7hnn+jzjv8QeGhSDTSBVh+Iy8HgwgjDTgo9Ejm3zX qsLsFAYdCZmoqAZs0QtJA2e3xwNY90g= ARC-Authentication-Results: i=1; imf08.hostedemail.com; dkim=pass header.d=deltatee.com header.s=20200525 header.b=EJgXMvWj; spf=pass (imf08.hostedemail.com: domain of logang@deltatee.com designates 204.191.154.188 as permitted sender) smtp.mailfrom=logang@deltatee.com; dmarc=pass (policy=none) header.from=deltatee.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1663946772; a=rsa-sha256; cv=none; b=lPJTXUG50x4OuEB37RZDvCTsXBXEs2F5J2VgpW+Wv5V/Zx6DEMzd/2KfJHqLVbAZEpC8C4 kluwYxUudztNAXkfymjT73j07yXP2jT9DyXlCwuj/3h0hvh5t3JNaMIPtuLAJWUf0ZtgG4 zmx/27fs5T7pFUwjpo/aPtwY4dZG2mE= Authentication-Results: imf08.hostedemail.com; dkim=pass header.d=deltatee.com header.s=20200525 header.b=EJgXMvWj; spf=pass (imf08.hostedemail.com: domain of logang@deltatee.com designates 204.191.154.188 as permitted sender) smtp.mailfrom=logang@deltatee.com; dmarc=pass (policy=none) header.from=deltatee.com X-Rspam-User: X-Stat-Signature: 5je5jdnucprakon5nm4gidcw9jcfcjjp X-Rspamd-Queue-Id: 51BB1160018 X-Rspamd-Server: rspam07 X-HE-Tag: 1663946770-117703 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 2022-09-23 00:01, Christoph Hellwig wrote: > Thanks, the entire series looks good to me now: > > Reviewed-by: Christoph Hellwig > > Given that this is spread all over, what tree do we want to take it > through? Yes, while this is ostensibly a feature for NVMe it turns out we didn't need to touch any NVMe code at all. The most likely patch in my mind to have conflicts is the iov_iter patch as there's been a lot of churn there in the last few cycles and there are continued discussions. There are 2 PCI patches, but Bjorn's aware of them and has acked them. I'm also fairly confident this shouldn't conflict with anything in his tree. Besides that, there is one mm/gup patch which is the next likely to conflict; one scatterlist patch and three block layer patches which have largely been stable when I've done rebases. Logan