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 D351CC433EF for ; Mon, 11 Apr 2022 06:56:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 77F526B0072; Mon, 11 Apr 2022 02:56:57 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 708666B0073; Mon, 11 Apr 2022 02:56:57 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5D21E6B0074; Mon, 11 Apr 2022 02:56:57 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0120.hostedemail.com [216.40.44.120]) by kanga.kvack.org (Postfix) with ESMTP id 4DE656B0072 for ; Mon, 11 Apr 2022 02:56:57 -0400 (EDT) Received: from smtpin29.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id DFA2493D67 for ; Mon, 11 Apr 2022 06:56:56 +0000 (UTC) X-FDA: 79343690832.29.B89D339 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by imf03.hostedemail.com (Postfix) with ESMTP id 892E620005 for ; Mon, 11 Apr 2022 06:56:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=BIRXrN6U5qu+MwEdPXUm3GcxOrtCsXQHomxMeDQj4iI=; b=cMqfbqPJ0PKcvMP2vBeOyQMy5M TJThlzGiOpD1xmxcofK4jvuO59I/BHGIexRKdZZhzlDw75gAhlLFe02EXS2k/fW7Qkk8BkbkaAP9p 1PiQIO8vPxJzSAZsCZ1H6cK4y9rBr1gSbYp7juhcHtSQVDbZUizws3gjKEommOF7lChe4sCVLrqEf VMY2SMl10YM145qLj9PamyqzKsZ+COY5SOtm6F0/BfB4TSLZ8cBxxYKPYM+DWVvhhNU/QZQXal5dc RduDnXNwHifDYR17YM9uC11abcyYPdSyBYla9PYFn5Bneskvcq/clp22VG6d0bsn5Zb101dIUpRHG mt3o/gHA==; Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1ndnyn-007123-1p; Mon, 11 Apr 2022 06:56:53 +0000 Date: Sun, 10 Apr 2022 23:56:52 -0700 From: Christoph Hellwig To: Song Liu Cc: Christoph Hellwig , Song Liu , "bpf@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-mm@kvack.org" , "ast@kernel.org" , "daniel@iogearbox.net" , "andrii@kernel.org" , Kernel Team , "akpm@linux-foundation.org" , "rick.p.edgecombe@intel.com" , "imbrenda@linux.ibm.com" Subject: Re: [PATCH bpf 2/2] bpf: use vmalloc with VM_ALLOW_HUGE_VMAP for bpf_prog_pack Message-ID: References: <20220408223443.3303509-1-song@kernel.org> <20220408223443.3303509-3-song@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: pdr9eqeo6ih1k3mq8yyhfewxqyqifxt6 Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=infradead.org header.s=bombadil.20210309 header.b=cMqfbqPJ; dmarc=none; spf=none (imf03.hostedemail.com: domain of BATV+28f505242231dd703457+6805+infradead.org+hch@bombadil.srs.infradead.org has no SPF policy when checking 198.137.202.133) smtp.mailfrom=BATV+28f505242231dd703457+6805+infradead.org+hch@bombadil.srs.infradead.org X-Rspamd-Queue-Id: 892E620005 X-HE-Tag: 1649660216-771370 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: On Sun, Apr 10, 2022 at 01:34:50AM +0000, Song Liu wrote: > OTOH, it is probably beneficial for the modules to use something > similar to bpf_prog_pack, i.e., put text from multiple modules to a > single huge page. Of course, this requires non-trivial work in both > mm code and module code. > > Given that 1) modules cannot use huge pages yet, and 2) module may > use differently (with sharing), I think adding module_alloc_large() > doesn't add much value at the moment. So we can just keep this logic > in BPF for now. > > Does this make sense? I'm not intending to say modules should use the new helper. But I'd much prefer to keep all the MODULES_VADDR related bits self-contained in the modules code and not splatter it over random other subsystems.