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 A0027CA9EB6 for ; Wed, 23 Oct 2019 12:04:57 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 71CD82064A for ; Wed, 23 Oct 2019 12:04:57 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 71CD82064A 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 2156F6B0003; Wed, 23 Oct 2019 08:04:57 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 19EFA6B0006; Wed, 23 Oct 2019 08:04:57 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 08D216B0007; Wed, 23 Oct 2019 08:04:57 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0128.hostedemail.com [216.40.44.128]) by kanga.kvack.org (Postfix) with ESMTP id D49926B0003 for ; Wed, 23 Oct 2019 08:04:56 -0400 (EDT) Received: from smtpin30.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with SMTP id 9407162F2 for ; Wed, 23 Oct 2019 12:04:56 +0000 (UTC) X-FDA: 76074918192.30.hook83_2b1c2e5fec42b X-HE-Tag: hook83_2b1c2e5fec42b X-Filterd-Recvd-Size: 1867 Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by imf16.hostedemail.com (Postfix) with ESMTP for ; Wed, 23 Oct 2019 12:04:56 +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 5E655AC4A; Wed, 23 Oct 2019 12:04:54 +0000 (UTC) Date: Wed, 23 Oct 2019 14:04:52 +0200 From: Michal Hocko To: Hillf Danton Cc: linux-mm , Andrew Morton , linux-kernel , Johannes Weiner , Shakeel Butt , Minchan Kim , Mel Gorman , Vladimir Davydov , Jan Kara Subject: Re: [RFC v1] mm: add page preemption Message-ID: <20191023120452.GN754@dhcp22.suse.cz> References: <20191022142802.14304-1-hdanton@sina.com> <20191023115350.4956-1-hdanton@sina.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191023115350.4956-1-hdanton@sina.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed 23-10-19 19:53:50, Hillf Danton wrote: > > On Wed, 23 Oct 2019 10:17:29 +0200 Michal Hocko wrote: [...] > > This doesn't really answer my question. > > Why cannot you use memcgs as they are now. > > No prio provided. > > > Why exactly do you need a fixed priority? > > Prio comparison in global reclaim is what was added. Because every task has > prio makes that comparison possible. That still doesn't answer the question because it doesn't explain why is the priority really necessary. I am sorry but I have more important things to deal with than asking the same question again and again. -- Michal Hocko SUSE Labs