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.5 required=3.0 tests=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 6A161C47404 for ; Fri, 4 Oct 2019 14:43:28 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 443E320659 for ; Fri, 4 Oct 2019 14:43:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 443E320659 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id E075F6B0006; Fri, 4 Oct 2019 10:43:27 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id DB5C68E0005; Fri, 4 Oct 2019 10:43:27 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CCBB98E0003; Fri, 4 Oct 2019 10:43:27 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0039.hostedemail.com [216.40.44.39]) by kanga.kvack.org (Postfix) with ESMTP id A8A1F6B0006 for ; Fri, 4 Oct 2019 10:43:27 -0400 (EDT) Received: from smtpin18.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with SMTP id 4907B180AD803 for ; Fri, 4 Oct 2019 14:43:27 +0000 (UTC) X-FDA: 76006370454.18.loss88_1e1be6502ad03 X-HE-Tag: loss88_1e1be6502ad03 X-Filterd-Recvd-Size: 1958 Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by imf20.hostedemail.com (Postfix) with ESMTP for ; Fri, 4 Oct 2019 14:43:26 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 9C2E2AC69; Fri, 4 Oct 2019 14:43:25 +0000 (UTC) Date: Fri, 4 Oct 2019 16:43:25 +0200 From: Michal Hocko To: Daniel Colascione Cc: "Kirill A. Shutemov" , Qian Cai , Tim Murray , Suren Baghdasaryan , linux-kernel , linux-mm Subject: Re: [PATCH] Make SPLIT_RSS_COUNTING configurable Message-ID: <20191004144325.GP9578@dhcp22.suse.cz> References: <1C584B5C-E04E-4B04-A3B5-4DC8E5E67366@lca.pw> <20191004123349.GB10845@dhcp22.suse.cz> <20191004132624.ctaodxaxsd7wzwlh@box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000031, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri 04-10-19 06:45:21, Daniel Colascione wrote: [...] > Nobody has demonstrated that split RSS accounting actually helps in > the real world. But I've described above, concretely, how split RSS > accounting hurts. I've been trying for over a year to either disable > split RSS accounting or to let people opt out of it. If you won't > remove split RSS accounting and you won't let me add a configuration > knob that lets people opt out of it, what will you accept? What is an argument to keep it around? -- Michal Hocko SUSE Labs