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 9BD07C43334 for ; Wed, 13 Jul 2022 13:56:48 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D66E3940136; Wed, 13 Jul 2022 09:56:47 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D1757940134; Wed, 13 Jul 2022 09:56:47 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BDFCE940136; Wed, 13 Jul 2022 09:56:47 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id AE43E940134 for ; Wed, 13 Jul 2022 09:56:47 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 88B4B2105E for ; Wed, 13 Jul 2022 13:56:47 +0000 (UTC) X-FDA: 79682227254.19.59B79EC Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) by imf27.hostedemail.com (Postfix) with ESMTP id 14D414007D for ; Wed, 13 Jul 2022 13:56:46 +0000 (UTC) Received: by mail-vs1-f42.google.com with SMTP id i186so10796571vsc.9 for ; Wed, 13 Jul 2022 06:56:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KmR3zIvPRcGHZ+9uuqzqrigy1eQiGWgglnEUCHnLRTw=; b=jqvCG36YrXa31HLHjFghK3hWp0U+tkXHjZdVEW4qnG45XLWlagRu0xQKCjI0TngXbX AhRqFz9i5hqrgoItpzy5asLZ4OkuTJ/jv5kuLXQEStM+aRGj1tF6cPnNvlPuQaWoBNZz 9gSfYBUqj4CU/It7BSTtoz22Pq2NuMdU+5rrVmAUNcDmPzDe96aReqXEWfUQT+Dzt0Iv 2W182CxYF1CAYX+jMbgQKDM7K35d35qedLTEQjd5D/5ScAL/kAve91pXJcs5XRHBkR0Z NOxmxUPeMrcd6MWG4a5/aPwYC7eiSZYZA3G96sOyEpBzr8xIpc64EHNFaExxN1cMzYTf p4wQ== 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=KmR3zIvPRcGHZ+9uuqzqrigy1eQiGWgglnEUCHnLRTw=; b=K5XacZOoRqopbWutY2lR5dv0b1rDGiSE+YwsLslD5vmRuRoPQpTjsv/S/jaN+Q/2VZ v2v2DeJB+aOK5I3F9CRurG17Isa6mtR34BqDy16lrJ1/Bth/F5/7cmtRfBfJo1rvaogQ NMHhgGBSY54ghMe4ACNu4QAMbBIr993A9tmnk/mhr+tgtfumscNyX61vWO10iXUhTspe Bfu14KbLfdYOeicUO2MVHYJuqzR0jnHBjMTwutIgRPKXjNuIwcpuX/aNnvhb03Zd3OB9 Q3g7Jok5qb9jT6yYaa+0kQFxLLgxSPcfmiV2QPMZv3f8H4wAR23KP+ZRbab+KV0qIFcs C+ow== X-Gm-Message-State: AJIora+kG/hPgOiDIpW0eAv03DDKyqtsaD0GFhzFKfxFqDRxusRd62Mw xcieRfN4fiWFnEPynrNLV0nlIFr39dM2w6YdmoM= X-Google-Smtp-Source: AGRyM1vjlYSXh2tsTBxNP1Xah71beC6fLMhLz1iiDXJ/EgZ1xZenJyUAOLTOoUvFkZwImz3TM/auk9bJ1jlWzbz6SbI= X-Received: by 2002:a05:6102:7b2:b0:357:6ab5:e1a5 with SMTP id x18-20020a05610207b200b003576ab5e1a5mr1432091vsg.22.1657720606255; Wed, 13 Jul 2022 06:56:46 -0700 (PDT) MIME-Version: 1.0 References: <20220712043914.pxmbm7vockuvpmmh@macbook-pro-3.dhcp.thefacebook.com> <20220712184315.k6tteikog7pze5z2@MacBook-Pro-3.local.dhcp.thefacebook.com> In-Reply-To: <20220712184315.k6tteikog7pze5z2@MacBook-Pro-3.local.dhcp.thefacebook.com> From: Yafang Shao Date: Wed, 13 Jul 2022 21:56:09 +0800 Message-ID: Subject: Re: [PATCH bpf-next 0/5] bpf: BPF specific memory allocator. To: Alexei Starovoitov Cc: Shakeel Butt , Tejun Heo , Mina Almasry , Michal Hocko , Yosry Ahmed , Muchun Song , Johannes Weiner , Matthew Wilcox , Christoph Hellwig , "David S. Miller" , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , bpf , Kernel Team , linux-mm , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , Vlastimil Babka Content-Type: text/plain; charset="UTF-8" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1657720607; a=rsa-sha256; cv=none; b=Eq2Z7PV2/bUw6N9n7PlXdsluSk5N7vyZnwqVQVQCP5550paRgfXv4KHbvOfr3bcKzJac7h 3b/L7HbXW2eZPMUDVEwW5BGhS89EzQkzfIkkzD65jxlFaDj1Vos4E95Qxw0Nv574QC/EAC E+NkZfUeNFvBXcAROWD3xU8D/z/NFnM= ARC-Authentication-Results: i=1; imf27.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=jqvCG36Y; spf=pass (imf27.hostedemail.com: domain of laoar.shao@gmail.com designates 209.85.217.42 as permitted sender) smtp.mailfrom=laoar.shao@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1657720607; h=from:from:sender: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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=KmR3zIvPRcGHZ+9uuqzqrigy1eQiGWgglnEUCHnLRTw=; b=Panl6Heu/R9flG7/pbkiuK25D+/KW+uCcOYgLxY5b54xRZCPLXOvOoMtscx67SAnm7k/ty 8wYr9UCrRI6hbpJHfhrAqwhNTJYoBy50S9IbmmcO82UsFnaUDUr4uCLjdS3n7lQycd8wpu wUjYYdlatZY/QF9kKNiJ0lFGVtIBxYU= X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 14D414007D X-Rspam-User: Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=jqvCG36Y; spf=pass (imf27.hostedemail.com: domain of laoar.shao@gmail.com designates 209.85.217.42 as permitted sender) smtp.mailfrom=laoar.shao@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Stat-Signature: 63uwchtyrkry4u31tinntpiq6rho51zk X-HE-Tag: 1657720606-445251 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 Wed, Jul 13, 2022 at 2:43 AM Alexei Starovoitov wrote: > > On Tue, Jul 12, 2022 at 11:11:25AM -0700, Shakeel Butt wrote: > > Ccing Mina who actually worked on upstreaming this. See [1] for > > previous discussion and more use-cases. > > > > [1] https://lore.kernel.org/linux-mm/20211120045011.3074840-1-almasrymina@google.com/ > > Doesn't look like that it landed upstream? > > For bpf side we're thinking of something similar. > We cannot do memcg= mount option, of course. > Instead memcg path or FD will passed to bpf side to be used later. > So the user can select a memcg instead of taking it from current. > > Yafang, > I'm assuming you're working on something like this? Yes, I'm working on it. I will post it once it is ready, but probably not shortly. -- Regards Yafang