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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2BD0BEB64DD for ; Fri, 21 Jul 2023 22:18:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230018AbjGUWSQ (ORCPT ); Fri, 21 Jul 2023 18:18:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60700 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229640AbjGUWSN (ORCPT ); Fri, 21 Jul 2023 18:18:13 -0400 Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D4C62D7C; Fri, 21 Jul 2023 15:17:55 -0700 (PDT) Received: by mail-pl1-x636.google.com with SMTP id d9443c01a7336-1b8ad8383faso17678695ad.0; Fri, 21 Jul 2023 15:17:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689977875; x=1690582675; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=Cjm6i6VGWK46ksrSf/WO54+zzsF5ULR5YF0/kPA+stI=; b=sIusdMkhzyYYzt7HTZ12ouC1zo0sibV8H/PYeYkaLxSBDEhc0NmcBhK/VXQFLOMD8W yS7JEFFOviSYIfM0AUhzG9IhwX1q9peWhyLEwZo1fi1Ei5S7h1BqDE1g6Of2+nZ7PTpx Q+UOBogLu+QuJl125anoYUSX9LRIuAPBV+8p+ObtmgkGeVXFhpawz5krJvA98tTOB6Ra lnn6h/GpqJu3CRz4orpNv/dF77t7/T6j5np29gkpvd7deyLug5Qg9GNsgFdanYl8stF4 TYc5U1LqMLuLF3QdZikaEvERFBL7v8REuiNxCz5F8AxJJI9Sl1vfdhCDfmupGEmdv0d9 iQvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689977875; x=1690582675; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Cjm6i6VGWK46ksrSf/WO54+zzsF5ULR5YF0/kPA+stI=; b=D1wNs4Y/uPVWUhpC5qT7XcImfXGnQd8SfM8nSSXRzseo+AqL0iFOniHo+TBVhW96mI mjCrZddYEUNOhQ86iLdM1TQM2nqufNq/NIiW61b+mA6CRtDuF0QaqrgwzRQCte3J/hww 2qzqjilBQsXqUgyZzZlnkkI4+dLQnbNAY9c4IfLedNKWdgWtkjqtFvOzfmmP2i/0PL36 gWtx+0Jv7kR1OMPXmZArT/nN9tFKZ2DXMJaGCr4U8WB6TM7/06NWDpu5AJqSKsJfQsIl /yoXRbrk04MQlRI65wGm5YLLe/80BeJbCR3vXHImjQuF4TD/FSwqZ1uLnnkBYaV97xBl pOkA== X-Gm-Message-State: ABy/qLZPvrO5RgpovNXC0roK/tjnfcIqe+2R/jY7ehp9kXhG40JIYFsv HVXsirI5w83MtJd44IiZ47s= X-Google-Smtp-Source: APBJJlFHfb0jG/WWODgMdRojw07Pd0F9ziQEPHIpWaqHWQMOzDHQ9v53Ib02LKyBkAYUj3LalcPxeA== X-Received: by 2002:a17:903:2304:b0:1bb:4861:d39e with SMTP id d4-20020a170903230400b001bb4861d39emr2970299plh.12.1689977874650; Fri, 21 Jul 2023 15:17:54 -0700 (PDT) Received: from localhost ([2620:10d:c090:400::5:fbd8]) by smtp.gmail.com with ESMTPSA id t11-20020a170902a5cb00b001b9dab0397bsm2339866plq.29.2023.07.21.15.17.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 21 Jul 2023 15:17:54 -0700 (PDT) Sender: Tejun Heo Date: Fri, 21 Jul 2023 12:17:53 -1000 From: Tejun Heo To: Tvrtko Ursulin Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, Johannes Weiner , Zefan Li , Dave Airlie , Daniel Vetter , Rob Clark , =?iso-8859-1?Q?St=E9phane?= Marchesin , "T . J . Mercier" , Kenny.Ho@amd.com, Christian =?iso-8859-1?Q?K=F6nig?= , Brian Welty , Tvrtko Ursulin , Michal =?iso-8859-1?Q?Koutn=FD?= Subject: Re: [PATCH 12/17] cgroup/drm: Introduce weight based drm cgroup control Message-ID: References: <20230712114605.519432-1-tvrtko.ursulin@linux.intel.com> <20230712114605.519432-13-tvrtko.ursulin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230712114605.519432-13-tvrtko.ursulin@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 12, 2023 at 12:46:00PM +0100, Tvrtko Ursulin wrote: > +DRM scheduling soft limits > +~~~~~~~~~~~~~~~~~~~~~~~~~~ Please don't say soft limits for this. It means something different for memcg, so it gets really confusing. Call it "weight based CPU time control" and maybe call the triggering points as thresholds. Thanks. -- tejun