linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add enospc_debug printing in metadata_reserve_bytes
Date: Fri, 15 Dec 2017 13:41:06 +0200	[thread overview]
Message-ID: <022899d1-e7f6-0cab-66f3-9753c6c9ea11@suse.com> (raw)
In-Reply-To: <67c2425e-c182-4223-fd04-603fade3bead@gmx.com>



On 15.12.2017 13:36, Qu Wenruo wrote:
> .
> 
> But btrfs_space_reservation() seems to be abused.
> Every type from delalloc to enospc debug will use it.
> 
> What about splitting them into different trace events?

I think trace events form some sort of an ABI so we can't really be
modifying current events, though I'd defer to David on that matter.

OTOH the trace event contains all the information we like - either if
it's an alloc/free operation, whether it's data or metadata and whether
it's enospc or not. Admittedly the last thing is a bit of a pain-point
since if you want to filter enospc you have to do string parsing on the
output from the trace_btrfs_space_reservation. But even this doesn't
sound too compelling to warrant a split. Either ways I'm fine with it.

  reply	other threads:[~2017-12-15 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 10:05 [PATCH] btrfs: Add enospc_debug printing in metadata_reserve_bytes Nikolay Borisov
2017-12-15 11:36 ` Qu Wenruo
2017-12-15 11:41   ` Nikolay Borisov [this message]
2018-02-05 16:20 ` Nikolay Borisov
2018-02-06  1:29   ` Qu Wenruo
2018-02-06  9:18     ` Nikolay Borisov
2018-02-14 13:13       ` 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=022899d1-e7f6-0cab-66f3-9753c6c9ea11@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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).