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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9ACAC433FE for ; Thu, 10 Nov 2022 22:08:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229719AbiKJWIN (ORCPT ); Thu, 10 Nov 2022 17:08:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33086 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229601AbiKJWIL (ORCPT ); Thu, 10 Nov 2022 17:08:11 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 28F6E2A94F for ; Thu, 10 Nov 2022 14:07:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1668118036; 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: in-reply-to:in-reply-to:references:references; bh=pkHFZ8A71PGLDYSbDeILz7gnWAG5cNe8osJEY2sw1oo=; b=RkPDbCDIgGFQcga5oWayTUjknIzkXHDLI0FMjgf7A4TRa2pWrtZCln2SF3EYMRCUfi1Mjs gT0/WhKBKmI/EFkX2LuMYKsdbe5KAZdugVBppd1ysgb8Qgke62L6vARMZ63RqqGlZrB+JE 7LPayI2GlR7NTMJT63mwjjkeTuofv1g= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-277-SaiWYo-ONkCeKDUEjDUSxA-1; Thu, 10 Nov 2022 17:07:15 -0500 X-MC-Unique: SaiWYo-ONkCeKDUEjDUSxA-1 Received: by mail-qv1-f72.google.com with SMTP id ng1-20020a0562143bc100b004bb706b3a27so2504690qvb.20 for ; Thu, 10 Nov 2022 14:07:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=pkHFZ8A71PGLDYSbDeILz7gnWAG5cNe8osJEY2sw1oo=; b=s/EPpnlbTJnt1LeYuVUlzcQFwmtoDH/emJPWDMw3o5gaYkiMG0d71kWDLrieS/fOo7 zaCsPKWDR+N5udd2C3aX1W66kfj+fDj9CPY/DiGwTPE1mwFco31irsGRx7EM/74v8egd j+SKVfhsR7wQqxPjxC/VryJy4ap8JYJ0jpy7fI10+G0nlG90DP84XuqHEEylOTcNGkrm JkuygOZ4HSnPqfdNSnj463dXhzb7xh6+1Yvel8KgKTKqUmFnnRAh/otUuXZe/+e7RSei yA2qFzIdyWYGeQwKD7xSfCCh3MKoJ2jWfBTJ7PeaGTwX4738Gv6fjhKnGNXziOe5r6AG Cp3Q== X-Gm-Message-State: ACrzQf0axxWoDtu78qZVUh1H7/fdR0EB/WrmHOOD0LqJyTTNI0YS/vDT ixXUCHxYJjlyJFb0+VK1HnZ+7BZ3PHPPpDX2sO57wXNFsIuby3C9P0sWUXhPcxzrxMTFjC3mWnP jDFma+Qgh1P3zFIFV X-Received: by 2002:a05:622a:a13:b0:3a5:7c31:2e3e with SMTP id bv19-20020a05622a0a1300b003a57c312e3emr1687902qtb.111.1668118034559; Thu, 10 Nov 2022 14:07:14 -0800 (PST) X-Google-Smtp-Source: AMsMyM4t4EgXmvKFwJ30gGMnTRs25++xa44a/3U/cSg3MHQzpqjLs+FQ2ezrzmzlOvCI1OHu38uacA== X-Received: by 2002:a05:622a:a13:b0:3a5:7c31:2e3e with SMTP id bv19-20020a05622a0a1300b003a57c312e3emr1687885qtb.111.1668118034342; Thu, 10 Nov 2022 14:07:14 -0800 (PST) Received: from x1n (bras-base-aurron9127w-grc-46-70-31-27-79.dsl.bell.ca. [70.31.27.79]) by smtp.gmail.com with ESMTPSA id y8-20020a05620a44c800b006ee77f1ecc3sm358268qkp.31.2022.11.10.14.07.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Nov 2022 14:07:13 -0800 (PST) Date: Thu, 10 Nov 2022 17:07:12 -0500 From: Peter Xu To: Mike Kravetz Cc: Nadav Amit , Linux-MM , kernel list , Naoya Horiguchi , David Hildenbrand , Axel Rasmussen , Mina Almasry , Rik van Riel , Vlastimil Babka , Matthew Wilcox , Andrew Morton , Wei Chen , stable@vger.kernel.org Subject: Re: [PATCH v8 1/2] hugetlb: don't delete vma_lock in hugetlb MADV_DONTNEED processing Message-ID: References: <20221108011910.350887-1-mike.kravetz@oracle.com> <20221108011910.350887-2-mike.kravetz@oracle.com> <9BB0EA0C-6E7C-462B-8374-5BFEC34E8415@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Thu, Nov 10, 2022 at 01:48:06PM -0800, Mike Kravetz wrote: > However, Peter seems to prefer just exposing the current zap_page_range_single. > The issue with exposing zap_page_range_single as it is today, is that we also > need to expose 'struct zap_details' which currently is not visible outside > mm/memory.c. Ah I see, that's okay to me. Thanks, -- Peter Xu