From: Anand Jain <anand.jain@oracle.com>
To: Boris Burkov <boris@bur.io>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 1/4] btrfs: use ffe_ctl in btrfs allocator tracepoints
Date: Fri, 18 Nov 2022 04:16:56 +0800 [thread overview]
Message-ID: <62ad323d-2199-4c79-b2b7-c8e9f4595255@oracle.com> (raw)
In-Reply-To: <ef44014bc0c5599a0cc7034d9912a4151e3c8e3b.1668626092.git.boris@bur.io>
On 11/17/22 03:22, Boris Burkov wrote:
> The allocator tracepoints currently have a pile of values from ffe_ctl.
> In modifying the allocator and adding more tracepoints, I found myself
> adding to the already long argument list of the tracepoints. It makes it
> a lot simpler to just send in the ffe_ctl itself.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
next prev parent reply other threads:[~2022-11-17 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 19:22 [PATCH v2 0/4] btrfs: data block group size classes Boris Burkov
2022-11-16 19:22 ` [PATCH v2 1/4] btrfs: use ffe_ctl in btrfs allocator tracepoints Boris Burkov
2022-11-17 7:33 ` Johannes Thumshirn
2022-11-17 20:16 ` Anand Jain [this message]
2022-11-18 16:51 ` David Sterba
2022-11-16 19:22 ` [PATCH v2 2/4] btrfs: add more ffe tracepoints Boris Burkov
2022-11-18 8:35 ` Johannes Thumshirn
2022-11-16 19:22 ` [PATCH v2 3/4] btrfs: introduce size class to block group allocator Boris Burkov
2022-11-16 19:22 ` [PATCH v2 4/4] btrfs: load block group size class when caching Boris Burkov
2022-11-17 9:12 ` kernel test robot
2022-11-17 9:22 ` kernel test robot
2022-11-18 16:56 ` [PATCH v2 0/4] btrfs: data block group size classes David Sterba
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=62ad323d-2199-4c79-b2b7-c8e9f4595255@oracle.com \
--to=anand.jain@oracle.com \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.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;
as well as URLs for NNTP newsgroup(s).