public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] veristat: add ability to sort by stat's absolute value
Date: Thu, 09 Nov 2023 18:20:25 +0000	[thread overview]
Message-ID: <169955402521.6918.2024940155187955055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231108051430.1830950-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 7 Nov 2023 21:14:29 -0800 you wrote:
> Add ability to sort results by absolute values of specified stats. This
> is especially useful to find biggest deviations in comparison mode. When
> comparing verifier change effect against a large base of BPF object
> files, it's necessary to see big changes both in positive and negative
> directions, as both might be a signal for regressions or bugs.
> 
> The syntax is natural, e.g., adding `-s '|insns_diff|'^` will instruct
> veristat to sort by absolute value of instructions difference in
> ascending order.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] veristat: add ability to sort by stat's absolute value
    https://git.kernel.org/bpf/bpf-next/c/dae6c6b3b79f
  - [bpf-next,2/2] veristat: add ability to filter top N results
    https://git.kernel.org/bpf/bpf-next/c/0ca98fca84b3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-11-09 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  5:14 [PATCH bpf-next 1/2] veristat: add ability to sort by stat's absolute value Andrii Nakryiko
2023-11-08  5:14 ` [PATCH bpf-next 2/2] veristat: add ability to filter top N results Andrii Nakryiko
2023-11-09 18:20 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=169955402521.6918.2024940155187955055.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox