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 73965ECAAA1 for ; Mon, 24 Oct 2022 15:03:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id DAAF3940008; Mon, 24 Oct 2022 11:03:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D5B4D940007; Mon, 24 Oct 2022 11:03:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C7210940008; Mon, 24 Oct 2022 11:03:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id B8572940007 for ; Mon, 24 Oct 2022 11:03:25 -0400 (EDT) Received: from smtpin17.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 736ACC0BC8 for ; Mon, 24 Oct 2022 15:03:25 +0000 (UTC) X-FDA: 80056161570.17.BDE9391 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf14.hostedemail.com (Postfix) with ESMTP id 9E4EF10002B for ; Mon, 24 Oct 2022 15:03:24 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 6EF1268BFE; Mon, 24 Oct 2022 17:03:20 +0200 (CEST) Date: Mon, 24 Oct 2022 17:03:20 +0200 From: Christoph Hellwig To: Logan Gunthorpe 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, Christoph Hellwig , Greg Kroah-Hartman , Dan Williams , Jason Gunthorpe , Christian =?iso-8859-1?Q?K=F6nig?= , 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 , viro@zeniv.linux.org.uk Subject: Re: [PATCH v11 0/9] Userspace P2PDMA with O_DIRECT NVMe devices Message-ID: <20221024150320.GA26731@lst.de> References: <20221021174116.7200-1-logang@deltatee.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221021174116.7200-1-logang@deltatee.com> User-Agent: Mutt/1.5.17 (2007-11-01) ARC-Authentication-Results: i=1; imf14.hostedemail.com; dkim=none; spf=none (imf14.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1666623804; a=rsa-sha256; cv=none; b=WrXNSova7keUpUMJ/i4kuIAeyB8Pta+kAshSQjX0us4bZSPUXRaTL2sEPO1k3YLljuV7Xs +WIcP+FfZBY4b4HeRVAgdoHBrg5i0rbDNMJmw6Wb2p7PK32fJtlufbPGfcAxtK6IRqj1ed ClOJbpxExlEGx810x1gqfsbjhn4aulA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1666623804; 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: in-reply-to:in-reply-to:references:references; bh=ohfolVyEwTGA6dZoX6saPhP2QSTVI2PE0ZFcdleLLMw=; b=YqSjqIuw/8sM3KG79n6kmAzubl8ORjvUPO/OicKjayVtEovrwQ5jwAx4tb32tuzKxfRhq8 keh4J7AcMLMTdDxg1K5ICBkqhaiUZgaXNozNoflPVXC+CgGiYJ3WsiT/gy0tc9E4KpbCoO 5UUYKKzW7TV9G4mftQQLODOE7MVkRdI= X-Stat-Signature: qg6y6kqhzxaxashoih4yqf5m66h7ioxa X-Rspamd-Queue-Id: 9E4EF10002B X-Rspam-User: Authentication-Results: imf14.hostedemail.com; dkim=none; spf=none (imf14.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de; dmarc=none X-Rspamd-Server: rspam06 X-HE-Tag: 1666623804-46125 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: The series looks good to me know. How do we want to handle it? I think we need a special branch somewhere (maybe in the block or mm trees?) so that we can base the other iov_iter work from John on it. Also Al has a whole bunch of iov_iter changes that we probably want on the same branch as well, although some of those (READ vs WRITE fixups) look like 6.1 material to me.