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 13BFFC433F5 for ; Tue, 5 Apr 2022 10:09:30 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 765C36B0073; Tue, 5 Apr 2022 06:09:20 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 73CAA6B0074; Tue, 5 Apr 2022 06:09:20 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 62BC66B0075; Tue, 5 Apr 2022 06:09:20 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) by kanga.kvack.org (Postfix) with ESMTP id 5371C6B0073 for ; Tue, 5 Apr 2022 06:09:20 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id 3224D8087C for ; Tue, 5 Apr 2022 10:09:10 +0000 (UTC) X-FDA: 79322402460.11.3997AD1 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf27.hostedemail.com (Postfix) with ESMTP id 850D840020 for ; Tue, 5 Apr 2022 10:09:09 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 4B8321F745; Tue, 5 Apr 2022 10:09:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1649153348; h=from:from:reply-to: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=s2JAhA7wRXjstDGSBxsda1XlMcvrnOLvDvnRGSGBhWQ=; b=VUzkhbo1IP8rBXBSTb+xi5+IO+JKiwE8GKiq1RV8GvLLp621TtLgWINmac+lMjA3AxHC7/ U+KDroTz7bzqhgUsS1Gvm4ACqI7ELwJOUTcIP0zkEutls9EakN7ohOic0E9tlWNymY7qr2 xEeaJnx+CzP6OJK8UrMwCtA0b8swnf8= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 0023613A04; Tue, 5 Apr 2022 10:09:07 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Bx79OkMVTGI0SQAAMHmgww (envelope-from ); Tue, 05 Apr 2022 10:09:07 +0000 Date: Tue, 5 Apr 2022 12:09:06 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: Shakeel Butt Cc: Wei Xu , Johannes Weiner , Yosry Ahmed , Michal Hocko , Andrew Morton , David Rientjes , Tejun Heo , Zefan Li , Roman Gushchin , Cgroups , "open list:DOCUMENTATION" , Linux Kernel Mailing List , Linux MM , Jonathan Corbet , Yu Zhao , Dave Hansen , Greg Thelen Subject: Re: [PATCH resend] memcg: introduce per-memcg reclaim interface Message-ID: <20220405100906.GB13806@blackbody.suse.cz> References: <20220331084151.2600229-1-yosryahmed@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Stat-Signature: 4e7fb4td67r6kf6newfq6btas8ztmwqf Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=VUzkhbo1; spf=pass (imf27.hostedemail.com: domain of mkoutny@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mkoutny@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com X-Rspam-User: X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 850D840020 X-HE-Tag: 1649153349-139843 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 Mon, Apr 04, 2022 at 10:08:43AM -0700, Shakeel Butt wrote: > What would be the challenge on returning the number of bytes reclaimed > through cgroup interface? You'd need an object that represents the write size: > bfd = open("/sys/kernel/mm/reclaim/balloon", O_RDWR); > dprintf(bfd, "type=file nodemask=1-2 timeout=30\n") > > fd = open("/sys/kernel/fs/cgroup/foo/memory.reclaim", O_WRONLY); > reclaimed = splice(bfd, NULL, fd, NULL, reclaim_size); (I'm joking with this API but it is a resembling concept.) Michal