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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 01FE9C433E0 for ; Thu, 11 Mar 2021 11:09:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 680E564EFD for ; Thu, 11 Mar 2021 11:09:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 680E564EFD Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id C22CD8D02AB; Thu, 11 Mar 2021 06:09:18 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id BFA598D028E; Thu, 11 Mar 2021 06:09:18 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A77168D02AB; Thu, 11 Mar 2021 06:09:18 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 884CB8D028E for ; Thu, 11 Mar 2021 06:09:18 -0500 (EST) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 4C900180ACEEC for ; Thu, 11 Mar 2021 11:09:18 +0000 (UTC) X-FDA: 77907321996.22.56BA3AF Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf04.hostedemail.com (Postfix) with ESMTP id D55463C0 for ; Thu, 11 Mar 2021 11:09:16 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1615460956; h=from:from:reply-to: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=6Ftb4gg7aNzOFmaBhKRMtFjVDjZpix86WNXDo3VsIpM=; b=TEB0emmNTwLphzFCW5mCrb6GRxhndTYFCHtZn9z7EFbHx5KgICDlDzhZHOUzQNksX4aGfZ 36L/3kX5dBoVGnMvkZMQV5hOiPRdoZfroHqtaleJIP3UjgAnnKSk6kxGDJmKQV6MqOuGJ5 nUqe+9rfadyyqC5zPHWIP0JoSaswsyc= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 3C201AB8C; Thu, 11 Mar 2021 11:09:16 +0000 (UTC) Date: Thu, 11 Mar 2021 12:09:15 +0100 From: Michal Hocko To: Peter Zijlstra Cc: Mike Kravetz , linux-mm@kvack.org, linux-kernel@vger.kernel.org, "Paul E . McKenney" , Shakeel Butt , tglx@linutronix.de, john.ogness@linutronix.de, urezki@gmail.com, ast@fb.com, Eric Dumazet , Mina Almasry , Andrew Morton Subject: Re: [PATCH] hugetlb: select PREEMPT_COUNT if HUGETLB_PAGE for in_atomic use Message-ID: References: <20210311021321.127500-1-mike.kravetz@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: 175h86wzagt6r1nmpif81tssr4mg879q X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: D55463C0 Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf04; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1615460956-976674 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 Thu 11-03-21 10:52:50, Peter Zijlstra wrote: > On Thu, Mar 11, 2021 at 10:44:56AM +0100, Michal Hocko wrote: > > On Thu 11-03-21 10:32:24, Peter Zijlstra wrote: > > > The whole changelog reads like a trainwreck, but akpm already commented > > > on that. I picked out a small factual incorrectness, simply because if > > > you can't get that right, the whole argument looses weight. > > > > Is there any reason why in_atomic || irq_disabled wouldn't work > > universally? > > I just explained to you how you really wanted: > > in_atomic() && !irq_disabled() Sorry for being dense but I do not follow. You have provided the following example spin_lock(&A); spin_lock(&A); if A == hugetlb_lock then we should never reenter with free_huge_page if (in_atomic() || irq_disabled()) schedule_in_wq(); else free_directly() because hugetlb_lock is never held in irq context other than from put_page (aka the above) path which will explicitly defer the handling and thus the lock to a different context. We need to check for irq_disabled because of the sleeping paths in the freeing path. Or do I miss something? >From the code simplicity POV (and hugetlb has grown a lot of complexity) it would be really easiest to make sure __free_huge_page to be called from a non-atomic process context. There are few ways to do that - defer each call to a WQ - user visible which sucks - defer from atomic or otherwise non-sleeping contextx - requires reliable in_atomic AFAICS - defer sleeping operations - makes the code flow more complex and it would be again user visible in some cases. So I would say we are in "pick your own poison" kind of situation. -- Michal Hocko SUSE Labs