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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9774FC7EE2E for ; Tue, 28 Feb 2023 13:51:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229677AbjB1NvE (ORCPT ); Tue, 28 Feb 2023 08:51:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229699AbjB1NvB (ORCPT ); Tue, 28 Feb 2023 08:51:01 -0500 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 058E0305E6; Tue, 28 Feb 2023 05:50:54 -0800 (PST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 9FA681FDC1; Tue, 28 Feb 2023 13:50:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1677592253; 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=a+axJ4fDmePQKpl5oDQ9xI+mAYeRUk3jBZn02hzcYwk=; b=IYQKcMF4XvBnvvKRj/q+4NsA4zlgvalUeOeZo1lBfkaF3u2BNeUHa15J5mK2wKQUGa2QzL 7DHSTLBQQX4mHTOkhneDNjY8k6kwgvqUD4TOa2szu510WQDdc/g+V5bXW+oLqUMQDQCzLK //rYSrtyAx9tgv/KUWmg5yxRdrZunok= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 798E913440; Tue, 28 Feb 2023 13:50:53 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id jU5ZG70G/mPKQQAAMHmgww (envelope-from ); Tue, 28 Feb 2023 13:50:53 +0000 Date: Tue, 28 Feb 2023 14:50:52 +0100 From: Michal Hocko To: Suren Baghdasaryan Cc: Sudarshan Rajagopalan , David Hildenbrand , Johannes Weiner , Mike Rapoport , Oscar Salvador , Anshuman Khandual , mark.rutland@arm.com, will@kernel.org, virtualization@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, Trilok Soni , Sukadev Bhattiprolu , Srivatsa Vaddagiri , Patrick Daly , johunt@akamai.com Subject: Re: [PATCH] psi: reduce min window size to 50ms Message-ID: References: <15cd8816-b474-0535-d854-41982d3bbe5c@quicinc.com> <82406da2-799e-f0b4-bce0-7d47486030d4@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 27-02-23 11:50:48, Suren Baghdasaryan wrote: > On Mon, Feb 27, 2023 at 11:11 AM Michal Hocko wrote: > > > > On Mon 27-02-23 09:49:59, Suren Baghdasaryan wrote: > > > On Mon, Feb 27, 2023 at 5:34 AM Michal Hocko wrote: > > > > > > > > On Fri 24-02-23 13:07:57, Suren Baghdasaryan wrote: > > > > > On Fri, Feb 24, 2023 at 4:47 AM Michal Hocko wrote: > > [...] > > > > > > Btw. it seems that there is is only a limit on a single trigger per fd > > > > > > but no limits per user so it doesn't sound too hard to end up with too > > > > > > much polling even with a larger timeouts. To me it seems like we need to > > > > > > contain the polling thread to be bound by the cpu controller. > > > > > > > > > > Hmm. We have one "psimon" thread per cgroup (+1 system-level one) and > > > > > poll_min_period for each thread is chosen as the min() of polling > > > > > periods between triggers created in that group. So, a bad trigger that > > > > > causes overly aggressive polling and polling thread being throttled, > > > > > might affect other triggers in that cgroup. > > > > > > > > Yes, and why that would be a problem? > > > > > > If unprivileged processes are allowed to add new triggers then a > > > malicious process can add a bad trigger and affect other legit > > > processes. That sounds like a problem to me. > > > > Hmm, I am not sure we are on the same page. My argument was that the > > monitoring kernel thread should be bound by the same cpu controller so > > even if it was excessive it would be bound to the cgroup constrains. > > Right. But if cgroup constraints are violated then the psimon thread's > activity will be impacted by throttling. In such cases won't that > affect other "good" triggers served by that thread even if they are > using higher polling periods? That is no different from any other part of the workload running within the same cpu bound cgroup running overboard with the cpu consumption. I do not see why psimon or anything else should be any different. Actually the only difference here is that the psi monitoring is outsourced to a kernel thread which is running ourside of any constrains. I am not sure where do we stand with kernel thread cpu cgroup accounting and I suspect this is not a trivial thing to do ATM. Hence longer term plan. -- Michal Hocko SUSE Labs