Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4378630ybl; Mon, 26 Aug 2019 09:32:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfhQQCngYcDDZLpZgj0Bm9fQnFyyV05ynrL9Zq7fjG4vo5EoGPzQTClUQFRQQfco8NSyiF X-Received: by 2002:a62:174a:: with SMTP id 71mr21784589pfx.140.1566837136359; Mon, 26 Aug 2019 09:32:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566837136; cv=none; d=google.com; s=arc-20160816; b=mJxSxci8tPW/zEyXGZD+fyefnq2/xJvwwcNY9sctKql/MOpBON14z6c0IcQbrSQKBF qVMc1e/Kc9hCVRLm5WqC6k/xuhAximOxTCz2M1tXDfFAHDDN4+NGVmtjrS4txVV0PkSP qPkxEqnK7+SEZwrMawM9hEjMli9LX8HrP8Bu/sywDLgQ2ElHJS96ydEbqHl8wcttZ6pD zN0v3M+f1E2HZiETZV9gGjoRhiWoAJOskiDGaCt0j82DrD4l+jSEs/S2NLnfM7QvdzX1 E37fcKlOAfLgoqcytN1WnH3RqIsg/AvJD30ItNUfTL0Qu8S+al5t/7izihkkyhzDLm6h AGHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:to:subject; bh=5VbHN80TRJRrA7qvqgXZI2T8R3L88DvE5Myv9XRasOQ=; b=pwtDjCopiLgks0yLQj6vVn4yr8cEzgTSuSTrShT2prov14qeLKdSm6Uznnqb5luZy8 ssWOhNbrp93dFHCK98odjIMBujYyVi/1Nk5s3+DrdPqfZZ2e5ESB39kQHZnD+XZPFed7 sFq9TQqU5taxoUiVY2We5vqR8CNMwRCZTi5nVV96xWRmFqKAnujdda8k/nJzlYpXMkNY CiwysQFE6CyLU2kT6aBPTeuT8U0NmUnxKvHoJfUgCErzmY4PzVhI7dUAqNOiMt/MAmHu mQ3iRXciEvN9NJmD3YpU8/CsXt+ZwQdg6yqgNK9Xfkg+M1sX5xgouQYeoi92OVvOxfnM wQ3Q== 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=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r3si10255678plb.14.2019.08.26.09.31.58; Mon, 26 Aug 2019 09:32:16 -0700 (PDT) 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=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732460AbfHZOZn (ORCPT + 99 others); Mon, 26 Aug 2019 10:25:43 -0400 Received: from out30-133.freemail.mail.aliyun.com ([115.124.30.133]:39063 "EHLO out30-133.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728155AbfHZOZn (ORCPT ); Mon, 26 Aug 2019 10:25:43 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R681e4;CH=green;DM=||false|;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01f04391;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=8;SR=0;TI=SMTPD_---0TaWxL0E_1566829535; Received: from IT-FVFX43SYHV2H.local(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0TaWxL0E_1566829535) by smtp.aliyun-inc.com(127.0.0.1); Mon, 26 Aug 2019 22:25:36 +0800 Subject: Re: [PATCH 00/14] per memcg lru_lock To: Daniel Jordan , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Mel Gorman , Tejun Heo , Michal Hocko References: <1566294517-86418-1-git-send-email-alex.shi@linux.alibaba.com> <6ba1ffb0-fce0-c590-c373-7cbc516dbebd@oracle.com> <348495d2-b558-fdfd-a411-89c75d4a9c78@linux.alibaba.com> From: Alex Shi Message-ID: <0f8e2bc0-96b4-f55a-51da-b53dac415dd7@linux.alibaba.com> Date: Mon, 26 Aug 2019 22:25:14 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2019/8/22 下午11:20, Daniel Jordan 写道: >> >>>    https://git.kernel.org/pub/scm/linux/kernel/git/wfg/vm-scalability.git/tree/case-lru-file-readtwice> >>> It's also synthetic but it stresses lru_lock more than just anon alloc/free.  It hits the page activate path, which is where we see this lock in our database, and if enough memory is configured lru_lock also gets stressed during reclaim, similar to [1]. >> >> Thanks for the sharing, this patchset can not help the [1] case, since it's just relief the per container lock contention now. > > I should've been clearer.  [1] is meant as an example of someone suffering from lru_lock during reclaim.  Wouldn't your series help per-memcg reclaim? yes, I got your point, since the aim9 don't show much improvement, I am trying this case in containers. Thanks Alex