linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: use the new helper wbc_to_write_flags
Date: Wed, 6 Sep 2017 15:28:31 -0700	[thread overview]
Message-ID: <20170906222831.GA16924@lim.localdomain> (raw)
In-Reply-To: <20170906143806.GQ31874@twin.jikos.cz>

On Wed, Sep 06, 2017 at 04:38:06PM +0200, David Sterba wrote:
> On Thu, Aug 24, 2017 at 06:19:48PM -0600, Liu Bo wrote:
> > This updates btrfs to use the helper wbc_to_write_flags which has been
> > applied in ext4/xfs/f2fs/block.
> 
> Added in commit 7637241e651ec36e4094 in 11/2016, I wonder why btrfs
> wasn't been changed as well as it uses the same code patterns as the
> other filesystems.
>

/me is curious, too.

> > Please note that, with this, btrfs's dirty pages written by a
> > writeback job will carry the flag REQ_BACKGROUND, which is currently
> > used by writeback-throttle to determine whether it should go to get a
> > request or wait.
> 
> Which in my understanding of the WBT behaviour is what we want, right?
>

Yes, it gives a hint to WBT whether it should wait or not.

> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> 
> Reviewed-by: David Sterba <dsterba@suse.com>
> 
> I'm still expecting some surprises (== performance drop) from the recent
> WBT changes, as we still may miss some request flags, but more subtle
> than eg. the superblock REQ_ tags.

Looks like this is the only missing flag I could find, the missing
REQ_META (in another patch) doesn't have an impact on WBT.

thanks,
-liubo

      reply	other threads:[~2017-09-06 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  0:19 [PATCH] Btrfs: use the new helper wbc_to_write_flags Liu Bo
2017-09-06 14:38 ` David Sterba
2017-09-06 22:28   ` Liu Bo [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=20170906222831.GA16924@lim.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --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).