From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-182.mta0.migadu.com (out-182.mta0.migadu.com [91.218.175.182]) (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 5729D4F5FB for ; Fri, 9 Aug 2024 17:40:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723225232; cv=none; b=e2zPFvdJehLNoPhhrDdXJP7hJTl2KIENXcQj/DA3DV8tXy6YJ6tlVuHz6WmEeoRnM5r+7gMjRRZdDyZsMThNzB7gWRxb8prUEjaQ1O/seUE/Tcm6mPmVdFrlXuDTiYdCapRSZY5dgdjgDcNFFyIXpbUZs8/j5hQAZLZIbc8tbLw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723225232; c=relaxed/simple; bh=mF9Rk9UqbmddH2smTFIewfkoo/OxomFe3j12CQIP7dA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=iEXm8E6PuQNsmE4bENJGp77+1KoPxEjD8W4W2Y5jCfq9rJzfFTvsGzqybi9srY0cmF4cTWS+IzHuHieLAQ+OB6/Or67H4mNxE97KcOQxHWjCijcNeIyYbrcEyirqZJcu5fHrVhfIMcXOsa8sicM1e2kuUTH3DJLgkA5fgXj3knA= 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=WAX3bpE6; arc=none smtp.client-ip=91.218.175.182 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="WAX3bpE6" Date: Fri, 9 Aug 2024 17:40:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1723225227; 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=YZCWqUJK1VMH5hpb/vZy61pLLKoniqi353OrzQ8BqKc=; b=WAX3bpE6p029ttYrP+yP1vcSR460iwdajJcW2JfUHhq9a82JkEst55U6Eu+IDbmaYGQFr3 JiLzr7LrNqvB05t+iEJYSshX6a9w+II7kLc06TESg9F32Zv0d2lnepiW4PwSGl/MqHhGL3 B297zGfB7RPgraQ/Cm2OO+ViUKJgLE4= 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 , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Meta kernel team , cgroups@vger.kernel.org, Matthew Wilcox Subject: Re: [PATCH] memcg: replace memcg ID idr with xarray Message-ID: References: <20240809172618.2946790-1-shakeel.butt@linux.dev> Precedence: bulk X-Mailing-List: cgroups@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: <20240809172618.2946790-1-shakeel.butt@linux.dev> X-Migadu-Flow: FLOW_OUT On Fri, Aug 09, 2024 at 10:26:18AM -0700, Shakeel Butt wrote: > At the moment memcg IDs are managed through IDR which requires external > synchronization mechanisms and makes the allocation code a bit awkward. > Let's switch to xarray and make the code simpler. > > Suggested-by: Matthew Wilcox > Signed-off-by: Shakeel Butt Sweet! Reviewed-by: Roman Gushchin