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 X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9CE4EC433E7 for ; Mon, 19 Oct 2020 13:38:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3C864208B3 for ; Mon, 19 Oct 2020 13:38:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="dbN5F1BO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728312AbgJSNh5 (ORCPT ); Mon, 19 Oct 2020 09:37:57 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:28289 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728258AbgJSNh5 (ORCPT ); Mon, 19 Oct 2020 09:37:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1603114676; h=from:from: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; bh=mS8bITCyzTOP2XiCenDLyc/N0OBdUAE0vG9p0LTiHC0=; b=dbN5F1BOOpQ1/0ptlzjrTNkjkrmgrgWaktiHCc7wu9jq0heMd/LwpwXn5xYonMv2HutO/T MrUiC+sZCM1xoAb27kDfYUei4oCRBs7yeCKlVx8gEmsWGvU46hxG1qWqQ0xeSDPZdX4eeC 947zmGPYaewBUQY1eqzvHNoCTNiSxdU= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-188-MkwAqYLAMgSr_4-1SRtEWw-1; Mon, 19 Oct 2020 09:37:54 -0400 X-MC-Unique: MkwAqYLAMgSr_4-1SRtEWw-1 Received: by mail-wr1-f72.google.com with SMTP id n14so7423585wrp.1 for ; Mon, 19 Oct 2020 06:37:53 -0700 (PDT) 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=mS8bITCyzTOP2XiCenDLyc/N0OBdUAE0vG9p0LTiHC0=; b=qe6/OgmHaagtIyM8vH18SmHjx+Iz5HMEfrB/E/t8XIk1x6Kkq8u5I2+Gsbl9+npHP4 FCXPM5SqXmTF85hhhw6nSkeAHHbNZa37Ncr2aAHvkXDCa/BtRfyVw5A8R6b2xFePO4Qh t7EIo/SdctlSObDl4fbf7m0F5s5ijtxAWYcLQoI/ae4LVBT5gqE25FRbAq4nqz0YdodB 4w1AAJswrtWAjWDAhOoCU3pAxHKhpgY8+ciP+XnJK9h8yYICO5g1KA3UIqXWsPiEuULf EhQ9uN1WtH6UWkvkG2OkOGHpHG329wQo9ijsN5o4DFFITM5oTsIg2lWpGl0jbBLPbp7X 7riw== X-Gm-Message-State: AOAM533tl7pAsKzAKhE71hchne1w8iXUrY1bM4y/cpA/vHr4bdT5BMWz VVnMeYk597MT545W10yhmXIVfuRNQ0mx+mOLFh53/J43MBPBj7XeLt/VCZ1BYsGzVwEAGXpwMJO xNgK/Ibf+iKiQ X-Received: by 2002:a5d:6cc8:: with SMTP id c8mr18748406wrc.233.1603114672884; Mon, 19 Oct 2020 06:37:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxAbCwKwVrnG9IjlEBOZo1+niRf9C9XuEZwHILJgt8/gQc3q9lqDdmd/vrjTfgDna8KJRZWMA== X-Received: by 2002:a5d:6cc8:: with SMTP id c8mr18748381wrc.233.1603114672632; Mon, 19 Oct 2020 06:37:52 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id x81sm81282wmb.11.2020.10.19.06.37.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Oct 2020 06:37:52 -0700 (PDT) Subject: Re: [PATCH 00/35] Enhance memory utilization with DMEMFS To: Dan Williams , Joao Martins Cc: yulei zhang , linux-fsdevel , kvm , LKML , Xiao Guangrong , Wanpeng Li , Haiwei Li , Yulei Zhang , Andrew Morton , Naoya Horiguchi , Al Viro , Matthew Wilcox , Mike Kravetz , Jane Y Chu , Muchun Song , Konrad Rzeszutek Wilk References: <98be093d-c869-941a-6dd9-fb16356f763b@oracle.com> From: Paolo Bonzini Message-ID: <3626f5ff-b6a0-0811-5899-703a0714897d@redhat.com> Date: Mon, 19 Oct 2020 15:37:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 15/10/20 00:25, Dan Williams wrote: > Now, with recent device-dax extensions, it > also has a coarse grained memory management system for physical > address-space partitioning and a path for struct-page-less backing for > VMs. What feature gaps remain vs dmemfs, and can those gaps be closed > with incremental improvements to the 2 existing memory-management > systems? If I understand correctly, devm_memremap_pages() on ZONE_DEVICE memory would still create the "struct page" albeit lazily? KVM then would use the usual get_user_pages() path. Looking more closely at the implementation of dmemfs, I don't understand is why dmemfs needs VM_DMEM etc. and cannot provide access to mmap-ed memory using remap_pfn_range and VM_PFNMAP, just like /dev/mem. If it did that KVM would get physical addresses using fixup_user_fault and never need pfn_to_page() or get_user_pages(). I'm not saying that would instantly be an approval, but it would make remove a lot of hooks. Paolo