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 119D7C433EF for ; Thu, 24 Feb 2022 12:30:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AEE6E8D0002; Thu, 24 Feb 2022 07:30:42 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id A9E0C8D0001; Thu, 24 Feb 2022 07:30:42 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 967508D0002; Thu, 24 Feb 2022 07:30:42 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 8A3428D0001 for ; Thu, 24 Feb 2022 07:30:42 -0500 (EST) Received: from smtpin15.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id 67850121457 for ; Thu, 24 Feb 2022 12:30:42 +0000 (UTC) X-FDA: 79177607124.15.94D332E Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by imf13.hostedemail.com (Postfix) with ESMTP id CD40C20012 for ; Thu, 24 Feb 2022 12:30:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1645705841; h=from:from:reply-to:subject:subject: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=AqOiTimbhwMR6JdlyxUT8Se6t3oyzrlLLdGUoWlPRkk=; b=CVa/RFcVCxPn0ReGZNyU/gE8fn57dAMeZD0hwC49HuhZWPQ0F806taj/eYfwnPBBhw0jFc Pp7ULH2oJVt0YBHxck+gm9g/aO3m5A1xEnxxViRYiUkrvKAdxkYGWJ9V3DCyV8dbNnJTf1 Jlg4kvleJKI1xLkvT+6g1Jr4cR6sY4w= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-125-Px0M8utHMYCc6ouXz-mjKA-1; Thu, 24 Feb 2022 07:30:36 -0500 X-MC-Unique: Px0M8utHMYCc6ouXz-mjKA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AC89C1854E27; Thu, 24 Feb 2022 12:30:34 +0000 (UTC) Received: from fuller.cnet (ovpn-112-2.gru2.redhat.com [10.97.112.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 66F5B7BB6C; Thu, 24 Feb 2022 12:30:34 +0000 (UTC) Received: by fuller.cnet (Postfix, from userid 1000) id 80720416D862; Thu, 24 Feb 2022 09:30:11 -0300 (-03) Date: Thu, 24 Feb 2022 09:30:11 -0300 From: Marcelo Tosatti To: Aaron Tomlin Cc: Frederic Weisbecker , Christoph Lameter , tglx@linutronix.de, mingo@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Phil Auld Subject: Re: [RFC PATCH] tick/sched: Ensure quiet_vmstat() is called when the idle tick was stopped too Message-ID: References: <20220203214339.1889971-1-atomlin@redhat.com> <20220217124729.GA743618@lothringen> <20220217142615.xqtiydixvnumyvei@ava.usersys.com> <20220217163205.GA748087@lothringen> <20220218125454.utlgmuhijklzr3if@ava.usersys.com> <20220219154616.pwsvh445x3vn7ltf@ava.usersys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b="CVa/RFcV"; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf13.hostedemail.com: domain of mtosatti@redhat.com has no SPF policy when checking 170.10.129.124) smtp.mailfrom=mtosatti@redhat.com X-Rspam-User: X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: CD40C20012 X-Stat-Signature: h1f3h1u4doif1h7aiz7xoqfnoo97ritj X-HE-Tag: 1645705841-702623 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, Feb 24, 2022 at 09:27:14AM -0300, Marcelo Tosatti wrote: > On Sat, Feb 19, 2022 at 03:46:16PM +0000, Aaron Tomlin wrote: > > On Fri 2022-02-18 12:54 +0000, Aaron Tomlin wrote: > > > On Thu 2022-02-17 17:32 +0100, Frederic Weisbecker wrote: > > > > > If I understand correctly, in the context of nohz_full, since such work is > > > > > deferred, it will only be handled in a scenario when the periodic/or > > > > > scheduling-clock tick is enabled i.e. the timer was reprogrammed on exit > > > > > from idle. > > > > > > > > Oh I see, it's a deferrable delayed work... > > > > Then I can see two other issues: > > > > > > > > 1) Can an interrupt in idle modify the vmstat and thus trigger the need to > > > > flush it? > > Yes. Page allocation and page freeing for example. > > 6 3730 ../mm/page_alloc.c <> > __mod_zone_freepage_state(zone, -(1 << order), > 4 1096 ../mm/page_alloc.c <<__free_one_page>> > __mod_zone_freepage_state(zone, -(1 << order), > > > > > I believe it's the case and then the problem goes beyond nohz_full > > > > because if the idle interrupt fired while the tick is stopped and didn't set > > > > TIF_RESCHED, we go back to sleep without calling quiet_vmstat(). > > > > > > Yes: e.g. a nohz_full CPU, in idle code, could indeed receive a reschedule > > > IPI; re-enable local IRQs and generic idle code sees the TIF_NEED_RESCHED > > > flag against the idle task. Additionally, the selected task could > > > indirectly released a few pages [to satisfy a low-memory condition] and > > > modify CPU-specific vmstat data i.e. vm_stat_diff[NR_FREE_PAGES]. > > > > > > > > > > 2) What if we are running task A in kernel mode while the tick is stopped > > > > (nohz_full). Task A modifies the vmstat and goes to userspace for a long > > > > while. > > > > Your patch fixes case 1) but not case 2). The problem is that TIMER_DEFERRABLE > > > > should really be about dynticks-idle only and not dynticks-full. I've always > > > > been afraid about enforcing that rule though because that would break old > > > > noise-free setups. But perhaps I should... Can't grasp the sentence above "The problem is that ...". What rule?