Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp476031ybt; Fri, 19 Jun 2020 06:25:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwch1bYAYxeS1NJwGGQHh02jkWoqDQJ0n1l4Scpi4ekwEieUPl/SPr4q/RfuvDHX+L5n7Eh X-Received: by 2002:a05:6402:699:: with SMTP id f25mr3276366edy.281.1592573159186; Fri, 19 Jun 2020 06:25:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592573159; cv=none; d=google.com; s=arc-20160816; b=RVXhqg/tmQgkF6PWVjm8CXNUBloFmBHWOTVymHfYlH0wbxcs1vywCdENJqjFEkteFN MJviXSETZtlEMOlS3clhdHSoRmGEJPJW8JZ1neFkX6tnOs8V5C+0mYzj6R9GGGjpQa4h zAIHRwyIuNHonvxxqBOFUs1fFBUuoaUWt+5uSQ4bsaUHs0OGbmAt3dwQOzAnqlCSOvTH lsxmC+u9togIgsWA059WGezGkcQUIN0r7Puw2/7033reDuW9Yd8HGaV7RirI8bD/Oz3p p8mUZLm9NIPWCB4gJ4W/85AUUhx3UKXT9nXEb0HshslvC1qDkWaS8NoVMk8e7FhFR4g6 RgcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=sGAv5hxymm6jana6AIRp5Ukr19t4MVeCM82RM2CZFTc=; b=O6tlZ91JIuGVrGA3QB9KXTE2+azbcWZod6MqXqnvZfrpKj/CHlD6CH+imaDsZFHYQs KIKWyUvm9uqSHOf3kppoYCPlLHaEfMLw9SZuiSMLaQiOXeo5Hp1CoC2U/ZYhdWDc/OQk 88WO/BPz6k2bGxefcDgnf7UqB3vrnIatmSplGlwIRBo0yh9HyCA3CBkDdt++T8XGMJE2 Zy8uNLa1K76sYnCWMSoo0exO5u3AV/XhMdOLukAnZ9SkgwyaEmD8hPf8v969tt1C0dsM KxAuT7IoN6QtoUfGDC+c8bzkvn2TkGk0/4CQzwJpBh3d4gYpSFw96SKlH2+V6wHfyX5P x1wA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s12si3662799ejx.234.2020.06.19.06.25.36; Fri, 19 Jun 2020 06:25:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732599AbgFSNXM (ORCPT + 99 others); Fri, 19 Jun 2020 09:23:12 -0400 Received: from mail.kernel.org ([198.145.29.99]:44484 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732503AbgFSNXL (ORCPT ); Fri, 19 Jun 2020 09:23:11 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9D80D21527; Fri, 19 Jun 2020 13:23:09 +0000 (UTC) Date: Fri, 19 Jun 2020 09:23:07 -0400 From: Steven Rostedt To: Qais Yousef Cc: Valentin Schneider , Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Ben Segall , Mel Gorman , Patrick Bellasi , Chris Redpath , Lukasz Luba , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] sched/uclamp: Protect uclamp fast path code with static key Message-ID: <20200619092307.3fc89312@oasis.local.home> In-Reply-To: <20200619125148.y4cq3hwllgozbutq@e107158-lin.cambridge.arm.com> References: <20200618195525.7889-1-qais.yousef@arm.com> <20200618195525.7889-3-qais.yousef@arm.com> <20200619125148.y4cq3hwllgozbutq@e107158-lin.cambridge.arm.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Jun 2020 13:51:48 +0100 Qais Yousef wrote: > > On 18/06/20 20:55, Qais Yousef wrote: > > > There is a report that when uclamp is enabled, a netperf UDP test > > > regresses compared to a kernel compiled without uclamp. > > > > > > https://lore.kernel.org/lkml/20200529100806.GA3070@suse.de/ > > > > > > > ISTR the perennial form for those is: https://lkml.kernel.org/r/ > > The link is correct permalinnk from lore and contains the message-id as Peter > likes and he has accepted this form before. > > If you look closely you'll see that what you suggest is just moving 'lkml' to > replace lore in the dns name and put an /r/. I don't see a need to enforce one > form over the other as the one I used is much easier to get. The two produce the same result, and I personally have used both. I'm starting to move over to lore over lkml, as that seems to be becoming the more popular form. > > If Peter really insists I'll be happy to change. But I agree, if Peter is insistent on lkml over lore, then it really doesn't make a difference to switch it. As I said, they are identical in what they produce. -- Steve