Received: by 2002:ac0:8c8e:0:0:0:0:0 with SMTP id r14csp129844ima; Wed, 6 Feb 2019 18:42:36 -0800 (PST) X-Google-Smtp-Source: AHgI3IbTCfV3CPbsnUFVL6XPPrE7vlZDDWES2iZ3LtUj4s2K+f3E/y1nKC7rqBhFFzbboqJ2Fq8Q X-Received: by 2002:a17:902:f24:: with SMTP id 33mr14151438ply.65.1549507356744; Wed, 06 Feb 2019 18:42:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549507356; cv=none; d=google.com; s=arc-20160816; b=KvZOHImdVS4HF+oBdfDIUrzzLZyFGUsCJFXdosm+sgavcbNpRXPHkPEZkNdeQ/iT1L sVAiBl0cK21BdaBjeaaG0jPdd1CC3cLaKSTGJwc8c9mIimlhFQvZaUocoMf23P9Bp803 Pa3fAG6T/2Am/jjLdK/+zQSkCgUzy1OtedZPGjoohx50Fac38THahOO9yOWZEJK2oj8e TVM1/Xr/t9oYB1IwH/Sdn15HNlDIMOn7JCadWGshQoHRqXht+hAm8NUKALhX0/EpZj7R CmvZZuLUaH+GDaZn/64iNf8kCi31PeM6B51/qLWfJ1Fepm1Pm/6CLau7h0UTY0zrnMcr tBew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:organization :references:in-reply-to:date:cc:to:from:subject:message-id; bh=wY22i9Lu/9vYtvd8t3OpcdDTuAI/7AD9Ow3yUTH7upc=; b=yOpW2od0vjrWu+n9HEPNb4Re52KW0QPI8OZcSm0Z7hJfOMdUq/O0+iYk9A38VycJhW t5OSTOcr6TflUi3VLl4O8jg+0HDWN1+xByFWExZlqRViU2L+6ejObYUYuNSysNGiHUeq 5X3caZXoNTav8vl/gFPqJF9BuSTR5Q3iwUZkepc8aZXloQw50BNDr33ygmGvWMxaYuvK bm5TsH/uoCv6BpVYRTV918dCcDZdXYxifzgZkY6o9rpXmx8BKo+lxbdl3kNhjLuh8wYi Z1CcrCWdntAEqqgPAdrx/JSaRUBgsvTxezuqzO87xKo6tYNjqNCvAV0CS1879p7baUi6 C3Kg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m3si6639094plt.394.2019.02.06.18.42.21; Wed, 06 Feb 2019 18:42:36 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726642AbfBGCmK (ORCPT + 99 others); Wed, 6 Feb 2019 21:42:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60626 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726245AbfBGCmK (ORCPT ); Wed, 6 Feb 2019 21:42:10 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 15A6C8AE76; Thu, 7 Feb 2019 02:42:09 +0000 (UTC) Received: from haswell-e.nc.xsintricity.com (ovpn-112-17.rdu2.redhat.com [10.10.112.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7A6FE179C9; Thu, 7 Feb 2019 02:42:06 +0000 (UTC) Message-ID: <658363f418a6585a1ffc0038b86c8e95487e8130.camel@redhat.com> Subject: Re: [LSF/MM TOPIC] Discuss least bad options for resolving longterm-GUP usage by RDMA From: Doug Ledford To: Dan Williams Cc: Jason Gunthorpe , Dave Chinner , Christopher Lameter , Matthew Wilcox , Jan Kara , Ira Weiny , lsf-pc@lists.linux-foundation.org, linux-rdma , Linux MM , Linux Kernel Mailing List , John Hubbard , Jerome Glisse , Michal Hocko Date: Wed, 06 Feb 2019 21:42:03 -0500 In-Reply-To: References: <20190205175059.GB21617@iweiny-DESK2.sc.intel.com> <20190206095000.GA12006@quack2.suse.cz> <20190206173114.GB12227@ziepe.ca> <20190206175233.GN21860@bombadil.infradead.org> <47820c4d696aee41225854071ec73373a273fd4a.camel@redhat.com> <01000168c43d594c-7979fcf8-b9c1-4bda-b29a-500efe001d66-000000@email.amazonses.com> <20190206210356.GZ6173@dastard> <20190206220828.GJ12227@ziepe.ca> <0c868bc615a60c44d618fb0183fcbe0c418c7c83.camel@redhat.com> Organization: Red Hat, Inc. Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-7DPuKcdbFR8/o52+ZlEI" User-Agent: Evolution 3.30.4 (3.30.4-1.fc29) Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 07 Feb 2019 02:42:09 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-7DPuKcdbFR8/o52+ZlEI Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2019-02-06 at 14:44 -0800, Dan Williams wrote: > On Wed, Feb 6, 2019 at 2:25 PM Doug Ledford wrote: > > Can someone give me a real world scenario that someone is *actually* > > asking for with this? >=20 > I'll point to this example. At the 6:35 mark Kodi talks about the > Oracle use case for DAX + RDMA. >=20 > https://youtu.be/ywKPPIE8JfQ?t=3D395 I watched this, and I see that Oracle is all sorts of excited that their storage machines can scale out, and they can access the storage and it has basically no CPU load on the storage server while performing millions of queries. What I didn't hear in there is why DAX has to be in the picture, or why Oracle couldn't do the same thing with a simple memory region exported directly to the RDMA subsystem, or why reflink or any of the other features you talk about are needed. So, while these things may legitimately be needed, this video did not tell me about how/why they are needed, just that RDMA is really, *really* cool for their use case and gets them 0% CPU utilization on their storage servers. I didn't watch the whole thing though. Do they get into that later on? Do they get to that level of technical discussion, or is this all higher level? --=20 Doug Ledford GPG KeyID: B826A3330E572FDD Key fingerprint =3D AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD --=-7DPuKcdbFR8/o52+ZlEI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEErmsb2hIrI7QmWxJ0uCajMw5XL90FAlxbmvsACgkQuCajMw5X L93hMg/+MsKeTSWBe23u1LbQAPXeHxl4k8Yi91H9RYq8vp1SWYqJCsGxRS8U07tS lYJcnjNYxdIjjUE35E7tTCVS8HzJ9Kyj6DmxGcErb6UAH0QY7QsSTxlS4kzYt4ea FArz31ERKCxfCy7wsryKHdthZ2tpChgZNFqKvklv9GI9hbq5dQB+GdAc6XPOB1K6 reIV0BEUGGuTJbEXLTra+pzikeJZ1yzvOs74qx1PAjvE+gxExRA+CfzndwkKCfgE wgDxfpma8S1bwc9fpke5ea/oQJXsnCBWm6BWpNWZws4/jvAveAWdGECscYiz/6Qu d5gB5hrR689voX0oivLCZ/PpFEngnOmbdruI1ESR4e3kscl+VmSj74CSOyEFv4cN t6A3HgESFXKg2/FR0zVTt1laJdOC3f50U7v946erbuYnLKEwTBKLPZvMRpFz8Wp/ NcVPUJXhgVI0mPDYMUATZ/DJhvPq1SQGhYkBNT524PeVLAh5Uk3NwKljZ8Ubkx3V ISJrWMBSk1G+CHctK6gzh9slamHgjXdw98vJomyxcjdVQFk6LFXk3zWTtOS51YbN EECT/GIgNJRGy8M+jJfO7NbIMh6DKbwBA2SaC3e0Fa2tA3p8KfQ/CgcvdURASvIJ XB51Q2p4hb/n4rr8H1305ZJDHnzEbLVyC4dvwLQ2PjU+OGs0iPk= =xZBH -----END PGP SIGNATURE----- --=-7DPuKcdbFR8/o52+ZlEI--