From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-188.mta1.migadu.com (out-188.mta1.migadu.com [95.215.58.188]) (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 9C1342D062F for ; Tue, 11 Nov 2025 18:59:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.188 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762887549; cv=none; b=VyOs1xik1mUkdqq/c86FmZ+kQwSzL0WIFn7QMnC/qbFtFcql9ywTPplsLux+r4g5r+iSiwYfZh1bpza50wKfzVfFE8OwqmrAd94C8vEJKjSjIH9j3c7C9qYde747Y0j4z6YkchE4dSYoRWy6cnxvVjR0LKf9G8/s1+JRp7Yk75o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762887549; c=relaxed/simple; bh=RDEhhL7l7kPj/j5hoC79iose1GSDWYP+9pR26ZYBlLA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=cVkr+LXO2I8NeRmtMYUvrE8bJqAtaXrCNvcIUJzHQPwGcPp5KK5VNxGxFYWqWFwp9NAXyOsNXwlpFB11auN07sEsNm/c3VRSqb9SSyK/yiOjIqQ/U72NVEsxVxToND6JrBiwatPhprxRrqV2bvQei8RW64taV0Y53e7vz0BcDx4= 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=YmQ8Ols3; arc=none smtp.client-ip=95.215.58.188 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="YmQ8Ols3" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1762887545; 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=RDEhhL7l7kPj/j5hoC79iose1GSDWYP+9pR26ZYBlLA=; b=YmQ8Ols3UwpD+qPU4OHg4WNSQibssV+Bra+pUVk0AXHSFzDthAXR7uBayhKd7t4NXw/F0A vBWsRP94pm9gc7xNRHdoNvpQ3RoM9ZJtxn012NB5lkbdl43KyFbCWIkYnMiwP5omqyQgpS DyM9vrgkaAuqAc3E+PgBPP8AExMdPmA= From: Roman Gushchin To: Shakeel Butt Cc: Andrew Morton , Johannes Weiner , Michal Hocko , Muchun Song , Harry Yoo , Qi Zheng , Vlastimil Babka , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, Meta kernel team Subject: Re: [PATCH 3/4] memcg: remove __mod_lruvec_state In-Reply-To: <20251110232008.1352063-4-shakeel.butt@linux.dev> (Shakeel Butt's message of "Mon, 10 Nov 2025 15:20:07 -0800") References: <20251110232008.1352063-1-shakeel.butt@linux.dev> <20251110232008.1352063-4-shakeel.butt@linux.dev> Date: Tue, 11 Nov 2025 10:58:57 -0800 Message-ID: <87fraks8em.fsf@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT Shakeel Butt writes: > The __mod_lruvec_state is already safe against irqs, so there is no > need to have a separate interface (i.e. mod_lruvec_state) which > wraps calls to it with irq disabling and reenabling. Let's rename > __mod_lruvec_state to mod_lruvec_state. > > Signed-off-by: Shakeel Butt Acked-by: Roman Gushchin