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 B840BC433F5 for ; Tue, 19 Apr 2022 19:21:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355678AbiDSTXp (ORCPT ); Tue, 19 Apr 2022 15:23:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40652 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239660AbiDSTXl (ORCPT ); Tue, 19 Apr 2022 15:23:41 -0400 Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4FAF410FF8 for ; Tue, 19 Apr 2022 12:20:58 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id q22so3521271ljh.10 for ; Tue, 19 Apr 2022 12:20:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/3mAvdy0ga85ggIH3HoGB0ePtskeVfNvDlSSUq9jS0A=; b=QvNx6FxecAp/z7mkZwwjndqXRE72gf91AcAXVa+k62ZgBfXGYm/WwmIqt/J18sYwhc i2StNOuJVaOsCjV7cve0T1U3qOs/WN1wFMwJTv6daJNph0klA03P+VQS+HViCxN/bhCX eLHeAXjYrEG6AHsQ2gChTGLFMTqfXijO7Vj+0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/3mAvdy0ga85ggIH3HoGB0ePtskeVfNvDlSSUq9jS0A=; b=D5xq3EsONVWzqjZkqlEcz8jg2p9WTkOuiubQ9ZOlI2mjmXyLJk4UOXh0LBjI1vEmPi ArQ4NMlx8THGM3p2amz02eTsj6vgmcs6/ZLIcm3kLvZtmQxVcFKS7K1SV4wu3Gl9wa79 psfZLQYIs63FwUEDynzZj/S7KElp+U1Wlzydrfu8xUhkMj1J+decm1yY9xfAjFiVPAiu O2CJPhzRN0S4JBL2Hr2TniqOE4Y2D5J70h2PjljaHbIi3602t0OuqDrKcQySykEfX6Vj 3JUWY92RBAZ6k0Ddp4yoGjW1oPgRgdR2HTGipjKm/GLsojZMejQWGBzWST0TKh+o9yft 0OZQ== X-Gm-Message-State: AOAM533IBYKGXqd+DrMSkBNDTcWD3zDwfPfEKC3lzq8SEz1DHGThh5Mq HxB0xx3pX+riP3cIjI1tzSyQcV9zgTG3gC/hipI= X-Google-Smtp-Source: ABdhPJxWOTz622CxqVrYivwjcjDzl1LliANJmHBEe40Icz/k2YuGlaP3C+eL01lysqM783yHcoon6w== X-Received: by 2002:a2e:9101:0:b0:24b:554b:1203 with SMTP id m1-20020a2e9101000000b0024b554b1203mr10919894ljg.508.1650396056610; Tue, 19 Apr 2022 12:20:56 -0700 (PDT) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com. [209.85.167.49]) by smtp.gmail.com with ESMTPSA id n17-20020a19ef11000000b0046ff45dc816sm1246123lfh.129.2022.04.19.12.20.56 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Apr 2022 12:20:56 -0700 (PDT) Received: by mail-lf1-f49.google.com with SMTP id p10so31107873lfa.12 for ; Tue, 19 Apr 2022 12:20:56 -0700 (PDT) X-Received: by 2002:a05:6512:3c93:b0:44b:4ba:c334 with SMTP id h19-20020a0565123c9300b0044b04bac334mr12102115lfv.27.1650396055810; Tue, 19 Apr 2022 12:20:55 -0700 (PDT) MIME-Version: 1.0 References: <20220415164413.2727220-1-song@kernel.org> <4AD023F9-FBCE-4C7C-A049-9292491408AA@fb.com> <88eafc9220d134d72db9eb381114432e71903022.camel@intel.com> In-Reply-To: From: Linus Torvalds Date: Tue, 19 Apr 2022 12:20:39 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 bpf 0/4] vmalloc: bpf: introduce VM_ALLOW_HUGE_VMAP To: Mike Rapoport Cc: Song Liu , "Edgecombe, Rick P" , "mcgrof@kernel.org" , "linux-kernel@vger.kernel.org" , "bpf@vger.kernel.org" , "hch@infradead.org" , "ast@kernel.org" , "daniel@iogearbox.net" , "linux-mm@kvack.org" , "song@kernel.org" , Kernel Team , "pmladek@suse.com" , "akpm@linux-foundation.org" , "hpa@zytor.com" , "dborkman@redhat.com" , "edumazet@google.com" , "bp@alien8.de" , "mbenes@suse.cz" , "imbrenda@linux.ibm.com" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 19, 2022 at 11:42 AM Mike Rapoport wrote: > > I'd say that bpf_prog_pack was a cure for symptoms and this project tries > to address more general problem. > But you are right, it'll take some time and won't land in 5.19. Just to update people: I've just applied Song's [1/4] patch, which means that the whole current hugepage vmalloc thing is effectively disabled (because nothing opts in). And I suspect that will be the status for 5.18, unless somebody comes up with some very strong arguments for (re-)starting using huge pages. Linus