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.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 08C56C43603 for ; Thu, 12 Dec 2019 21:04:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C6207206DA for ; Thu, 12 Dec 2019 21:04:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="bcQhnECL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730985AbfLLVEe (ORCPT ); Thu, 12 Dec 2019 16:04:34 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:29126 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730919AbfLLVEe (ORCPT ); Thu, 12 Dec 2019 16:04:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576184673; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=01NNIM8ig03VvR+04+Um5NpONpr5COaZWoXIKz7Tp0M=; b=bcQhnECLNIQ5tYwK9olS305GXsm2E2EpM3/sebsCcCQg2+qFkpAACiCto6J+2gUkiODZ0c EyB5uDurqZCL/oMTQwtoeOKaith3uYslirMvf3PXpKAsnSM/yVnR/VPCqqlft2/sXSwcmC YZ8xkHxFXDzNoxA0TuZKjT2dlTjXPS0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-345-CDYG4b1SPSy8fX6ul2NrFw-1; Thu, 12 Dec 2019 16:04:32 -0500 X-MC-Unique: CDYG4b1SPSy8fX6ul2NrFw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 809438DA469; Thu, 12 Dec 2019 21:04:30 +0000 (UTC) Received: from llong.remote.csb (dhcp-17-59.bos.redhat.com [10.18.17.59]) by smtp.corp.redhat.com (Postfix) with ESMTP id C705110013A1; Thu, 12 Dec 2019 21:04:29 +0000 (UTC) Subject: Re: [PATCH v2] mm/hugetlb: defer free_huge_page() to a workqueue From: Waiman Long To: Mike Kravetz , Andrew Morton , Matthew Wilcox , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Michal Hocko , aneesh.kumar@linux.ibm.com References: <20191211194615.18502-1-longman@redhat.com> <4fbc39a9-2c9c-4c2c-2b13-a548afe6083c@oracle.com> <32d2d4f2-83b9-2e40-05e2-71cd07e01b80@redhat.com> <0fcce71f-bc20-0ea3-b075-46592c8d533d@oracle.com> <20191212060650.ftqq27ftutxpc5hq@linux-p48b> <20191212063050.ufrpij6s6jkv7g7j@linux-p48b> <20191212190427.ouyohviijf5inhur@linux-p48b> <79d3a7e1-384b-b759-cd84-56253fb9ed40@redhat.com> Organization: Red Hat Message-ID: <3bdddd47-c93e-6549-d36f-8eb8e8d9be12@redhat.com> Date: Thu, 12 Dec 2019 16:04:29 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <79d3a7e1-384b-b759-cd84-56253fb9ed40@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/12/19 3:52 PM, Waiman Long wrote: > On 12/12/19 2:22 PM, Mike Kravetz wrote: >> On 12/12/19 11:04 AM, Davidlohr Bueso wrote: >>> There have been deadlock reports[1, 2] where put_page is called >>> from softirq context and this causes trouble with the hugetlb_lock, >>> as well as potentially the subpool lock. >>> >>> For such an unlikely scenario, lets not add irq dancing overhead >>> to the lock+unlock operations, which could incur in expensive >>> instruction dependencies, particularly when considering hard-irq >>> safety. For example PUSHF+POPF on x86. >>> >>> Instead, just use a workqueue and do the free_huge_page() in regular >>> task context. >>> >>> [1] https://lore.kernel.org/lkml/20191211194615.18502-1-longman@redhat.com/ >>> [2] https://lore.kernel.org/lkml/20180905112341.21355-1-aneesh.kumar@linux.ibm.com/ >>> >>> Reported-by: Waiman Long >>> Reported-by: Aneesh Kumar K.V >>> Signed-off-by: Davidlohr Bueso >> Thank you Davidlohr. >> >> The patch does seem fairly simple and straight forward. I need to brush up >> on my workqueue knowledge to provide a full review. >> >> Longman, >> Do you have a test to reproduce the issue? If so, can you try running with >> this patch. > Yes, I do have a test that can reproduce the issue. I will run it with > the patch and report the status tomorrow. I don't think Davidlohr's patch is ready for prime time yet. So I will wait until a better version is available. Cheers, Longman