From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AAC3B18C93B for ; Fri, 25 Oct 2024 17:42:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729878139; cv=none; b=GZK9KeYKdxhecszlgFu1sdj+JRa27CbZzqFnwqmdvpgq+exyRrgMBb3fOQC6WR5BS0MlRos8GhaB3pzqIAQi6ecYE+2FRabsBc5Zgr5nuWNK2alLv6eWKURclcseTImzl5m/crbOaIHylOQW47OYAbtXY8easjB4OCxWj/G/Ghw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729878139; c=relaxed/simple; bh=iE39Vb1X4T0jx9k/rB0q9QuL77oR684C5JeaYBJ0y6M=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=EcVxRIdQB5wEpkzEcdnwlYUIpuHInLXaI0ncAyR0WSDoW9qfTvK8rofPti/C0e7FA8zJ6LaLXhkWhE45syVQv1zhwtTm6hlaAUgRwsAh37wsFJtr8cue/5cBs8ZQ2tzp+Kh0/O5t20s+IAKVOEjnJbsRn+miN/926py9eU0akD4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=e+6NTFgU; arc=none smtp.client-ip=91.218.175.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="e+6NTFgU" Date: Fri, 25 Oct 2024 17:42:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1729878134; h=from:from:reply-to:subject:subject: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=PxAiJN7w6LU2rGTtXb1kZ2rrUkO4O+COn4J7JMgPnnk=; b=e+6NTFgUQnMqlmx5R+riMuKXMi8dImOz9FDK87l7IOK0fizqnFXMjwHeQCLd/KMcsKiOcg lRcnTdRaFiPYzNCqhsiiT5bYfljUxTHDFLOriQjp6BoWt1ShXBuGLBsAruNYQPz+NZLlcZ 27u2DAu9JoXOWlIkJ00Zwziqi85rTMg= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Roman Gushchin To: Shakeel Butt Cc: Andrew Morton , Johannes Weiner , Michal Hocko , Muchun Song , Hugh Dickins , Yosry Ahmed , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org, Meta kernel team Subject: Re: [PATCH v1 6/6] memcg-v1: remove memcg move locking code Message-ID: References: <20241025012304.2473312-1-shakeel.butt@linux.dev> <20241025012304.2473312-7-shakeel.butt@linux.dev> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241025012304.2473312-7-shakeel.butt@linux.dev> X-Migadu-Flow: FLOW_OUT On Thu, Oct 24, 2024 at 06:23:03PM -0700, Shakeel Butt wrote: > The memcg v1's charge move feature has been deprecated. All the places > using the memcg move lock, have stopped using it as they don't need the > protection any more. Let's proceed to remove all the locking code > related to charge moving. > > Signed-off-by: Shakeel Butt Reviewed-by: Roman Gushchin