linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: <kernel-team@fb.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: add a flags field to btrfs_transaction
Date: Fri, 25 Sep 2015 09:38:01 -0400	[thread overview]
Message-ID: <56054E39.4090407@fb.com> (raw)
In-Reply-To: <CAHji153OssW8n0ukTeiYk+2dgSmB0Wcfzy=b7P5fnh370929bg@mail.gmail.com>

On 09/25/2015 08:30 AM, Holger Hoffstätte wrote:
> Followup from my observation wrt. "Btrfs: change how we wait for
> pending ordered extents" and balance sitting idle:
>
> On Thu, Sep 24, 2015 at 4:47 PM, Josef Bacik <jbacik@fb.com> wrote:
>> I want to set some per transaction flags, so instead of adding yet another int
>> lets just convert the current two int indicators to flags and add a flags field
>> for future use.  Thanks,
>
> ..snip..
>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index ff64689..3f5a781 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -1399,7 +1399,7 @@ again:
>>                  btrfs_error(root->fs_info, ret,
>>                              "Failed to remove dev extent item");
>>          } else {
>> -               trans->transaction->have_free_bgs = 1;
>> +               set_bit(BTRFS_TRANS_DIRTY_BG_RUN, &trans->transaction->flags);
>
> Judging from the rest of the code transformation TRANS_DIRTY_BG_RUN
> seems like the wrong bit to set here. A quick test with
> set_bit(BTRFS_TRANS_HAVE_FREE_BGS) confirms that it fixes the balance
> delays.

Haha oops, thanks for catching that, I'll fix it up locally and send out 
an updated one in a bit.

Josef


  reply	other threads:[~2015-09-25 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 14:47 [PATCH] Btrfs: add a flags field to btrfs_transaction Josef Bacik
2015-09-25 12:30 ` Holger Hoffstätte
2015-09-25 13:38   ` Josef Bacik [this message]
2015-09-25 14:52 ` [PATCH V2] " Josef Bacik

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=56054E39.4090407@fb.com \
    --to=jbacik@fb.com \
    --cc=holger.hoffstaette@googlemail.com \
    --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).