Received: by 2002:a17:90a:9103:0:0:0:0 with SMTP id k3csp1193003pjo; Wed, 8 Jan 2020 13:34:07 -0800 (PST) X-Google-Smtp-Source: APXvYqx5qeOe429g581375b1Oq+VFJFU3VViGtVZAOR1rWvr/QrpG3LMztN/Vth4hMFWEOG3oy0w X-Received: by 2002:a05:6830:2099:: with SMTP id y25mr5423894otq.87.1578519247763; Wed, 08 Jan 2020 13:34:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578519247; cv=none; d=google.com; s=arc-20160816; b=QGODcpieTqFChP8GaR/Lvwtfz03Ja9DKQZLiFKaBBABfXw/2XTk7gH5lSikc8sk5mQ Y5EN4uYyzxtDppXBx6D1N+u5b+/CSO8Cnpx4dmJrqrNynzLRPYjiFHgleNXrvksXzSDZ 8cQD++9kkGsIYVTL9ej679jfoquYX47uC/adLFdz08QfIdagKnCWr7rfM1KJehbh3BM8 NMPYaStdeCFgU0UwwUyOLbBFuEH2CKIBUQLrX/HbyKNKvXmi+z9aZoIacasfvs5rRkbr cCr1zRjAUBuDL5FsG0i/YfpoB9M7SX++FWAZ6AXCK3rfwVcXomlc2eCbkJbgEZk06z5q k8iA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=RQqfgknDaIjb21+Gp60OmaeCEwQMsp/RXY7IO5FUl3I=; b=ue1iHqwGeuKD5LHb6wTKGd41/Okbu1owVOrU7Qjr/5+BKfWWJjLRWTR4wmVWXU+Qap hWorAnsvfDFfz+gYEVM2jIkVwfBy3onWwUeBurT93iJcYLdWSDHX+RrwSBrc7REP2V61 8QfecjZ79PLdG2Aw/NK4+RkEphknJkMT9FitzsSACQK0k8vakwsudL1l5akQFRQatCNB wicXSB3B7CfTYges3Dk2epn7cddTmuAGQXXDzATl+2kVAF1D0E0TsJq0o15KoqcKzSvX RxxT9Bihl/rAJ0iUb34Rqreo0D0v0mYm7l/tw4R/4P+JeFacqDKODBmrg3/Y16xpAsA3 lIIg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h125si2152103oia.253.2020.01.08.13.33.55; Wed, 08 Jan 2020 13:34:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726694AbgAHVb5 (ORCPT + 99 others); Wed, 8 Jan 2020 16:31:57 -0500 Received: from mga17.intel.com ([192.55.52.151]:38087 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726179AbgAHVb5 (ORCPT ); Wed, 8 Jan 2020 16:31:57 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2020 13:31:57 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,411,1571727600"; d="scan'208";a="395875074" Received: from romley-ivt3.sc.intel.com ([172.25.110.60]) by orsmga005.jf.intel.com with ESMTP; 08 Jan 2020 13:31:56 -0800 Date: Wed, 8 Jan 2020 13:42:51 -0800 From: Fenghua Yu To: Reinette Chatre Cc: Shakeel Butt , Borislav Petkov , LKML , Thomas Gleixner , Ingo Molnar , x86@kernel.org Subject: Re: [bug report] resctrl high memory comsumption Message-ID: <20200108214250.GB40461@romley-ivt3.sc.intel.com> References: <20200108202311.GA40461@romley-ivt3.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 08, 2020 at 12:42:17PM -0800, Reinette Chatre wrote: > Hi Fenghua, > On 1/8/2020 12:23 PM, Fenghua Yu wrote: > > On Wed, Jan 08, 2020 at 09:07:41AM -0800, Shakeel Butt wrote: > >> Recently we had a bug in the system software writing the same pids to > >> the tasks file of resctrl group multiple times. The resctrl code > > Subject: [RFC PATCH] x86/resctrl: Fix redundant task movements > I think your fix would address this specific use case but a slightly > different use case will still encounter the problem of high memory > consumption. If for example, sleeping tasks are moved (many times) > between resource or monitoring groups then their task_works queue would > just keep growing. It seems that a call to task_work_cancel() before > adding a new work item should address all these cases? The checking code in this patch is also helpful to avoid redundant task move preparation (kzalloc(), task_work_add(), etc) in the same rdtgroup. How about adding both the checking code and task_work_cancel()? Thanks. -Fenghua