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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1749FC433EF for ; Fri, 27 May 2022 08:39:53 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 329C88D0003; Fri, 27 May 2022 04:39:52 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2D9388D0001; Fri, 27 May 2022 04:39:52 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1EA368D0003; Fri, 27 May 2022 04:39:52 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 0FB7F8D0001 for ; Fri, 27 May 2022 04:39:52 -0400 (EDT) Received: from smtpin29.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id DB19F810BB for ; Fri, 27 May 2022 08:39:51 +0000 (UTC) X-FDA: 79510874982.29.1DBFB63 Received: from outbound-smtp28.blacknight.com (outbound-smtp28.blacknight.com [81.17.249.11]) by imf26.hostedemail.com (Postfix) with ESMTP id 1D74E140004 for ; Fri, 27 May 2022 08:39:46 +0000 (UTC) Received: from mail.blacknight.com (pemlinmail04.blacknight.ie [81.17.254.17]) by outbound-smtp28.blacknight.com (Postfix) with ESMTPS id 5E5E9CCC03 for ; Fri, 27 May 2022 09:39:49 +0100 (IST) Received: (qmail 13188 invoked from network); 27 May 2022 08:39:49 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.198.246]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 27 May 2022 08:39:49 -0000 Date: Fri, 27 May 2022 09:39:46 +0100 From: Mel Gorman To: Qian Cai Cc: Andrew Morton , Nicolas Saenz Julienne , Marcelo Tosatti , Vlastimil Babka , Michal Hocko , LKML , Linux-MM Subject: Re: [PATCH 0/6] Drain remote per-cpu directly v3 Message-ID: <20220527083946.GF3441@techsingularity.net> References: <20220512085043.5234-1-mgorman@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 1D74E140004 X-Rspam-User: Authentication-Results: imf26.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf26.hostedemail.com: domain of mgorman@techsingularity.net designates 81.17.249.11 as permitted sender) smtp.mailfrom=mgorman@techsingularity.net X-Stat-Signature: mdfnze8cam4woxazir45pf9xfzzitxs4 X-Rspamd-Server: rspam05 X-HE-Tag: 1653640786-141462 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, May 26, 2022 at 01:19:38PM -0400, Qian Cai wrote: > On Thu, May 12, 2022 at 09:50:37AM +0100, Mel Gorman wrote: > > Changelog since v2 > > o More conversions from page->lru to page->[pcp_list|buddy_list] > > o Additional test results in changelogs > > > > Changelog since v1 > > o Fix unsafe RT locking scheme > > o Use spin_trylock on UP PREEMPT_RT > > > > This series has the same intent as Nicolas' series "mm/page_alloc: Remote > > per-cpu lists drain support" -- avoid interference of a high priority > > task due to a workqueue item draining per-cpu page lists. While many > > workloads can tolerate a brief interruption, it may be cause a real-time > > task runnning on a NOHZ_FULL CPU to miss a deadline and at minimum, > > the draining in non-deterministic. > > > > Currently an IRQ-safe local_lock protects the page allocator per-cpu lists. > > The local_lock on its own prevents migration and the IRQ disabling protects > > from corruption due to an interrupt arriving while a page allocation is > > in progress. The locking is inherently unsafe for remote access unless > > the CPU is hot-removed. > > > > This series adjusts the locking. A spinlock is added to struct > > per_cpu_pages to protect the list contents while local_lock_irq continues > > to prevent migration and IRQ reentry. This allows a remote CPU to safely > > drain a remote per-cpu list. > > > > This series is a partial series. Follow-on work should allow the > > local_irq_save to be converted to a local_irq to avoid IRQs being > > disabled/enabled in most cases. Consequently, there are some TODO comments > > highlighting the places that would change if local_irq was used. However, > > there are enough corner cases that it deserves a series on its own > > separated by one kernel release and the priority right now is to avoid > > interference of high priority tasks. > > > > Patch 1 is a cosmetic patch to clarify when page->lru is storing buddy pages > > and when it is storing per-cpu pages. > > > > Patch 2 shrinks per_cpu_pages to make room for a spin lock. Strictly speaking > > this is not necessary but it avoids per_cpu_pages consuming another > > cache line. > > > > Patch 3 is a preparation patch to avoid code duplication. > > > > Patch 4 is a simple micro-optimisation that improves code flow necessary for > > a later patch to avoid code duplication. > > > > Patch 5 uses a spin_lock to protect the per_cpu_pages contents while still > > relying on local_lock to prevent migration, stabilise the pcp > > lookup and prevent IRQ reentrancy. > > > > Patch 6 remote drains per-cpu pages directly instead of using a workqueue. > > Mel, we saw spontanous "mm_percpu_wq" crash on today's linux-next tree > while running CPU offlining/onlining, and wondering if you have any > thoughts? > Do you think it's related to the series and if so why? From the warning, it's not obvious to me why it would be given that it's a warning about a task not being inactive when it is expected to be. -- Mel Gorman SUSE Labs