Message ID | 20221017103806.2479139-1-zhengyejian1@huawei.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4ac7:0:0:0:0:0 with SMTP id y7csp1237341wrs; Sun, 16 Oct 2022 19:40:04 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7QqOMLOVrRTSzddZHHjYUkqmOjzNtNJLFVem5kGZeIMTv2Hqfo8MvdYT7SXrTM2Ma7f5hb X-Received: by 2002:a63:4752:0:b0:439:5dcc:fd78 with SMTP id w18-20020a634752000000b004395dccfd78mr8511976pgk.104.1665974404358; Sun, 16 Oct 2022 19:40:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665974404; cv=none; d=google.com; s=arc-20160816; b=C3ojZxoK33ORiioVROpNVsCWXAKC8vEf9ba3z58q3ZUiHTXrxl4EmGzjz1sLXWcyi0 +ZJTKaDhMn2LHrm92u84SHFKOTAAL34MTDbv/F+m0+PpZ1v0lguCCEsON1DfAdTl5z1k k3w3IBDkUyk+oaLBndrlqE2AoyfEi68gWkdh/CDF/nRV5bV9e0+AsDw+zJPR8eFTH94M uyVmAjkAXjEOQYjBfJ3wQ7H89AFwFIEh0tnig4Jxp+aXizrtfZLvrzlFDdC+S2Zn+19/ z8Q3nfnj8SUu7NeDUdflcu4U9Aljxx0JxhTaYkcx1qFxqnl8ifIVB+rC71691FQRiZGY +oAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=NOElf3FmEP99wg8d4GZydL4HZrCro0YrhiJ8kjg6trw=; b=Od292TEvHVSZS/gGAZdd7U+1HtLQia04qMpwE4EVOcDcfD8UZ578RCug3scGbdjmdC l644zjOjKksu0tiEBCSgkigFUpSjG4VLh9Yc751NxGSfT8wkNZz0rbAWCgp/Z15iEgyp fTuYEoLHTgn0I1+SPC5pe2M8SRDTYg0t33+mrc1KuwVfZX7DI6PxHsx0TCAwmueQ0C+O uqQEJMhH6+8EZjFtHOnsHui+x4d3HX/Vns+4myIlQXsrlqyZjY4gkgpevyPiXYvOMaCc e/3oX6onH8YHHNx3fNoUAuhzYt4br38qYxjLbeIzHn/WP++8jrAeSfMxI9QX2lzdLFwK LtIQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j13-20020a65430d000000b0046040a85ea6si10676285pgq.120.2022.10.16.19.39.51; Sun, 16 Oct 2022 19:40:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231149AbiJQCje (ORCPT <rfc822;ouuuleilei@gmail.com> + 99 others); Sun, 16 Oct 2022 22:39:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49814 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231144AbiJQCj0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sun, 16 Oct 2022 22:39:26 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 804C246225; Sun, 16 Oct 2022 19:39:17 -0700 (PDT) Received: from dggpeml500026.china.huawei.com (unknown [172.30.72.57]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4MrLhb377zzpVqg; Mon, 17 Oct 2022 10:35:59 +0800 (CST) Received: from dggpeml100012.china.huawei.com (7.185.36.121) by dggpeml500026.china.huawei.com (7.185.36.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 17 Oct 2022 10:38:43 +0800 Received: from localhost.localdomain (10.67.175.61) by dggpeml100012.china.huawei.com (7.185.36.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 17 Oct 2022 10:38:43 +0800 From: Zheng Yejian <zhengyejian1@huawei.com> To: <rostedt@goodmis.org>, <mhiramat@kernel.org>, <corbet@lwn.net>, <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <tom.zanussi@linux.intel.com> CC: <zhengyejian1@huawei.com> Subject: [PATCH -next] tracing/histogram: Update document for KEYS_MAX size Date: Mon, 17 Oct 2022 10:38:06 +0000 Message-ID: <20221017103806.2479139-1-zhengyejian1@huawei.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.67.175.61] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpeml100012.china.huawei.com (7.185.36.121) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DATE_IN_FUTURE_06_12, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1746900777073057055?= X-GMAIL-MSGID: =?utf-8?q?1746900777073057055?= |
Series |
[-next] tracing/histogram: Update document for KEYS_MAX size
|
|
Commit Message
Zheng Yejian
Oct. 17, 2022, 10:38 a.m. UTC
After commit 4f36c2d85ced ("tracing: Increase tracing map KEYS_MAX size"),
'keys' supports up to three fields.
Signed-off-by: Zheng Yejian <zhengyejian1@huawei.com>
---
Documentation/trace/histogram.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
On Mon, 17 Oct 2022 10:38:06 +0000 Zheng Yejian <zhengyejian1@huawei.com> wrote: > After commit 4f36c2d85ced ("tracing: Increase tracing map KEYS_MAX size"), > 'keys' supports up to three fields. This looks good to me. Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Steve, do you this this document fix should go into the stable trees? Thank you, > > Signed-off-by: Zheng Yejian <zhengyejian1@huawei.com> > --- > Documentation/trace/histogram.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histogram.rst > index c1b685a38f6b..87bd772836c0 100644 > --- a/Documentation/trace/histogram.rst > +++ b/Documentation/trace/histogram.rst > @@ -39,7 +39,7 @@ Documentation written by Tom Zanussi > will use the event's kernel stacktrace as the key. The keywords > 'keys' or 'key' can be used to specify keys, and the keywords > 'values', 'vals', or 'val' can be used to specify values. Compound > - keys consisting of up to two fields can be specified by the 'keys' > + keys consisting of up to three fields can be specified by the 'keys' > keyword. Hashing a compound key produces a unique entry in the > table for each unique combination of component keys, and can be > useful for providing more fine-grained summaries of event data. > -- > 2.25.1 >
On Wed, 19 Oct 2022 00:31:34 +0900 Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote: > On Mon, 17 Oct 2022 10:38:06 +0000 > Zheng Yejian <zhengyejian1@huawei.com> wrote: > > > After commit 4f36c2d85ced ("tracing: Increase tracing map KEYS_MAX size"), > > 'keys' supports up to three fields. > > This looks good to me. > > Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Thanks Masami. > > Steve, do you this this document fix should go into the stable trees? We could label it as stable. Sure. Jon, do you want to tag this for stable and pull it through your tree? Should probably add a Fixes tag with the above commit. -- Steve > > Thank you, > > > > > Signed-off-by: Zheng Yejian <zhengyejian1@huawei.com> > > --- > > Documentation/trace/histogram.rst | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histogram.rst > > index c1b685a38f6b..87bd772836c0 100644 > > --- a/Documentation/trace/histogram.rst > > +++ b/Documentation/trace/histogram.rst > > @@ -39,7 +39,7 @@ Documentation written by Tom Zanussi > > will use the event's kernel stacktrace as the key. The keywords > > 'keys' or 'key' can be used to specify keys, and the keywords > > 'values', 'vals', or 'val' can be used to specify values. Compound > > - keys consisting of up to two fields can be specified by the 'keys' > > + keys consisting of up to three fields can be specified by the 'keys' > > keyword. Hashing a compound key produces a unique entry in the > > table for each unique combination of component keys, and can be > > useful for providing more fine-grained summaries of event data. > > -- > > 2.25.1 > > > >
Steven Rostedt <rostedt@goodmis.org> writes: > On Wed, 19 Oct 2022 00:31:34 +0900 > Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote: > >> On Mon, 17 Oct 2022 10:38:06 +0000 >> Zheng Yejian <zhengyejian1@huawei.com> wrote: >> >> > After commit 4f36c2d85ced ("tracing: Increase tracing map KEYS_MAX size"), >> > 'keys' supports up to three fields. >> >> This looks good to me. >> >> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> > > Thanks Masami. > >> >> Steve, do you this this document fix should go into the stable trees? > > We could label it as stable. Sure. > > Jon, do you want to tag this for stable and pull it through your tree? Sure, I can do that. Thanks, jon
On Tue, 18 Oct 2022 09:49:51 -0600 Jonathan Corbet <corbet@lwn.net> wrote: > > Jon, do you want to tag this for stable and pull it through your tree? > > Sure, I can do that. Thanks Jon! -- Steve
diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histogram.rst index c1b685a38f6b..87bd772836c0 100644 --- a/Documentation/trace/histogram.rst +++ b/Documentation/trace/histogram.rst @@ -39,7 +39,7 @@ Documentation written by Tom Zanussi will use the event's kernel stacktrace as the key. The keywords 'keys' or 'key' can be used to specify keys, and the keywords 'values', 'vals', or 'val' can be used to specify values. Compound - keys consisting of up to two fields can be specified by the 'keys' + keys consisting of up to three fields can be specified by the 'keys' keyword. Hashing a compound key produces a unique entry in the table for each unique combination of component keys, and can be useful for providing more fine-grained summaries of event data.