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 X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88B10C35242 for ; Sat, 8 Feb 2020 21:41:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 99F7E24650 for ; Sat, 8 Feb 2020 21:41:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727542AbgBHVlu (ORCPT ); Sat, 8 Feb 2020 16:41:50 -0500 Received: from gentwo.org ([3.19.106.255]:41332 "EHLO gentwo.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727473AbgBHVlu (ORCPT ); Sat, 8 Feb 2020 16:41:50 -0500 Received: by gentwo.org (Postfix, from userid 1002) id 535B33F3D6; Sat, 8 Feb 2020 21:41:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id 510343F242; Sat, 8 Feb 2020 21:41:49 +0000 (UTC) Date: Sat, 8 Feb 2020 21:41:49 +0000 (UTC) From: Christopher Lameter X-X-Sender: cl@www.lameter.com To: Wen Yang cc: Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , Xunlei Pang , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/slub: Detach node lock from counting free objects In-Reply-To: <5373ce28-c369-4e40-11dd-b269e4d2cb24@linux.alibaba.com> Message-ID: References: <20200201031502.92218-1-wenyang@linux.alibaba.com> <5373ce28-c369-4e40-11dd-b269e4d2cb24@linux.alibaba.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 8 Feb 2020, Wen Yang wrote: > I would greatly appreciate it if you kindly give me some feedback on this > patch. I think the measure is too severe given its use and the general impact on code. Maybe avoid taking the lock or reducing the time a lock is taken when reading /proc/slabinfo is the best approach? Also you could cache the value in the userspace application? Why is this value read continually?