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=-11.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL 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 27CA3C433DF for ; Thu, 4 Jun 2020 19:20:26 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id DC400206E6 for ; Thu, 4 Jun 2020 19:20:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="R+Yz0Foz" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DC400206E6 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 70E3480007; Thu, 4 Jun 2020 15:20:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 6C0318E0006; Thu, 4 Jun 2020 15:20:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5AE4B80007; Thu, 4 Jun 2020 15:20:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0227.hostedemail.com [216.40.44.227]) by kanga.kvack.org (Postfix) with ESMTP id 44AE18E0006 for ; Thu, 4 Jun 2020 15:20:25 -0400 (EDT) Received: from smtpin06.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 06FA27FD84 for ; Thu, 4 Jun 2020 19:20:25 +0000 (UTC) X-FDA: 76892495610.06.glue31_47116cc26d99 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin06.hostedemail.com (Postfix) with ESMTP id D1C2B10216E43 for ; Thu, 4 Jun 2020 19:20:24 +0000 (UTC) X-HE-Tag: glue31_47116cc26d99 X-Filterd-Recvd-Size: 6203 Received: from mail-wm1-f66.google.com (mail-wm1-f66.google.com [209.85.128.66]) by imf45.hostedemail.com (Postfix) with ESMTP for ; Thu, 4 Jun 2020 19:20:24 +0000 (UTC) Received: by mail-wm1-f66.google.com with SMTP id c71so6300443wmd.5 for ; Thu, 04 Jun 2020 12:20:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ouAgXFl2oDrnxvULrGgv6WgEdc2JkyMXoReqxIRdap0=; b=R+Yz0FozPBPFPWc9NPwI1q5KqS9DoWZ/gt2LO6RAy54U7fhmfoVIQx4iJFexNJvfwh o2w8wi/pvxVgDgw+7urh6y2tN4oEuicJLi65AOGp58A1yEiCZjPGole59Qj9LfFL5m0u okppwEX3a7ZzsWzYHtsiE6A9XfOw6cmaOBdT8jPp3vd12VzXvCPVukPWaXuMLrHFJWWR tvs3N0hTMVfY4Ykwrq3C82U0R3yCNN5T1ioQqvuD1ERevyIa5MFgw9DFQc73DIfMWHvI WDbPuDBFGWZcG7w/LmJyW/1A64WcKkyCWXrMukydp5ce4Cfeq9nsXl1kiXNT6zLS/Tks wZXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ouAgXFl2oDrnxvULrGgv6WgEdc2JkyMXoReqxIRdap0=; b=DmiFWehUBYr2Q3L+PaPrJ6bBapLL8SAnjPg3pd8lQ8CuK8UebERwB4yWh6LvE6INIx WxZn2sPUeb7Z1Pnva5YI07C28yL7KlYybH2GLtUeJgEg55uJer3zC03LUNpqxGUXLZFm cKvWlgD3VqkUKkOJirn8G08+m4R9KyG8mcZiUHq+WPtyakMkwDqrT72aZb21vI8pZ98/ CG+x9XAEugzepfCicshBS1nmIMw2JXd8VAWG3LWi9er5W0d6MW8KstNlxULTOhc0Ao9C uCmWDbr0Yqpb8UYTf5q+DBOKovIPFDN+kyCL0+xJjmiTXxjQqldZfWJ71qB5jPdXebbg 3KSQ== X-Gm-Message-State: AOAM531/w7zw8c8sO+CScc5nfTyjzgXjM6uNu7gVLPqljnKQEJrqfvY9 GTs/0NJLq9uzK7zcL9zNENAxJPJIZivK+libpAzqlQ== X-Google-Smtp-Source: ABdhPJw23Qj+XqKUo8d9Yi8zLVFZDmhHc9ZyRZ5y8DYBKe3GyWRTZppjy7dTb8VyjV1fNr9PaqujNnTfPtIXywE5Tec= X-Received: by 2002:a1c:6884:: with SMTP id d126mr5337742wmc.121.1591298422679; Thu, 04 Jun 2020 12:20:22 -0700 (PDT) MIME-Version: 1.0 References: <20200528195442.190116-1-surenb@google.com> <20200604131215.GB4117@hirez.programming.kicks-ass.net> In-Reply-To: <20200604131215.GB4117@hirez.programming.kicks-ass.net> From: Suren Baghdasaryan Date: Thu, 4 Jun 2020 12:20:10 -0700 Message-ID: Subject: Re: [PATCH 1/1] psi: eliminate kthread_worker from psi trigger scheduling mechanism To: Peter Zijlstra Cc: Ingo Molnar , Johannes Weiner , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Benjamin Segall , mgorman@suse.de, Shakeel Butt , linux-mm , LKML , kernel-team Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: D1C2B10216E43 X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam04 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, Jun 4, 2020 at 6:12 AM Peter Zijlstra wrote: > > On Thu, May 28, 2020 at 12:54:42PM -0700, Suren Baghdasaryan wrote: > > Each psi group requires a dedicated kthread_delayed_work and > > kthread_worker. Since no other work can be performed using psi_group's > > kthread_worker, the same result can be obtained using a task_struct and > > a timer directly. This makes psi triggering simpler by removing lists > > and locks involved with kthread_worker usage and eliminates the need for > > poll_scheduled atomic use in the hot path. > > > > Signed-off-by: Suren Baghdasaryan > > --- > > This patch is meant to address Peter's request in [1] to pull > > kthread_queue_delayed_work() out from under rq->lock. This should also address > > the lockdep warning about possibility of a circular dependency described in [2] > > I think you could've just fixed kthread_queue_delayed_work(), that code > is sub-optimal. Ok, let me look into it some more. My understanding was that the worker->lock in kthread_queue_delayed_work() was needed to synchronize worker->delayed_work_list access. But maybe I'm missing something... I assume you are talking about optimizing this beyond what https://lkml.org/lkml/2020/5/4/1148 was doing? BTW, any objections against taking https://lkml.org/lkml/2020/5/4/1148 ? It's not the ultimate fix but it is an improvement since it gets some of the operations that were unnecessarily under worker->lock out of it. > > But I suppose this works too. In PSI's case there is always one work for each worker, so the delayed_work_list and work_list are not needed and therefore I can replace kthread_worker machinery with a task and a timer. I think I can simplify this a bit further. For example group->poll_wakeup doesn't have to be an atomic. Originally I wanted to avoid a possibility of a race when poll_timer_fn sets it and psi_poll_worker resets it and as a result misses a wakeup, however if psi_poll_worker resets it before calling psi_poll_work then there is no harm in missing a wakeup because we called psi_poll_work and did the required work anyway. One question about this patch I'm not sure about and wanted to ask you Peter is whether it's ok to call mod_timer from within a hotpath (while holding rq->lock). As I described in the additional comment, there is a possibility of a race between when I check timer_pending and the call to mod_timer, so it's possible that mod_timer might be called both from psi_poll_work (psi poll work handler) and from psi_task_change (hotpath under rq->lock). I see that mod_timer takes base->lock spinlock, and IIUC such a race might block the hotpath and therefore is unacceptable. If this is true I'll need to revive the poll_scheduled atomic to close this race and then I can change mod_timer into add_timer. WDYT? And sorry for my ignorance if this is a trivial question. I'm not sure about the rules when it comes to rq->locks. Thanks, Suren. > > -- > To unsubscribe from this group and stop receiving emails from it, send an email to kernel-team+unsubscribe@android.com. >