From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/3] Btrfs: remove nr_async_bios
Date: Fri, 29 Sep 2017 18:28:00 -0700 [thread overview]
Message-ID: <20170930012800.GA20449@lim.localdomain> (raw)
In-Reply-To: <20170927113013.GY31640@twin.jikos.cz>
On Wed, Sep 27, 2017 at 01:30:13PM +0200, David Sterba wrote:
> On Thu, Sep 07, 2017 at 11:22:20AM -0600, Liu Bo wrote:
> > This was intended to congest higher layers to not send bios, but as
> >
> > 1) the congested bit has been taken by writeback
>
> Can you please be more specific here?
>
Sure, async bios comes from buffered writes and DIO writes.
For DIO writes, we want to submit them ASAP, while for buffered
writes, writeback uses balance_dirty_pages() to throttle how much
dirty pages we can have.
> > 2) and no one is waiting for %nr_async_bios down to zero,
> >
> > we can safely remove this now.
>
> From the original commit it looks like mechanism to avoid some write
> patterns (streaming not becoming random), but the commit is from 2008,
> lot of things have changed.
I did check the history, but have to check it again before typing the
following...
IIUC, it was introduced along with changes which makes checksumming
workload spread accross different cpus. And at that time, seems
pdflush is used instead of per-bdi flush, perhaps pdflush doesn't have
the necessary information for writeback to do throttling, Chris should
answer this better.
>
> I think we should at least document whats' the congestion behaviour we
> rely on nowadays, so that' sfor the 1). Otherwise patch looks ok.
>
Sounds good.
> >
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > fs/btrfs/ctree.h | 1 -
> > fs/btrfs/disk-io.c | 1 -
> > fs/btrfs/volumes.c | 14 --------------
> > 3 files changed, 16 deletions(-)
> >
> > diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> > index 3f3eb7b..27cd882 100644
> > --- a/fs/btrfs/ctree.h
> > +++ b/fs/btrfs/ctree.h
> > @@ -881,7 +881,6 @@ struct btrfs_fs_info {
> >
> > atomic_t nr_async_submits;
> > atomic_t async_submit_draining;
> > - atomic_t nr_async_bios;
> > atomic_t async_delalloc_pages;
> > atomic_t open_ioctl_trans;
> >
> > diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> > index f45b61f..95583e2 100644
> > --- a/fs/btrfs/disk-io.c
> > +++ b/fs/btrfs/disk-io.c
> > @@ -2657,7 +2657,6 @@ int open_ctree(struct super_block *sb,
> > atomic_set(&fs_info->nr_async_submits, 0);
> > atomic_set(&fs_info->async_delalloc_pages, 0);
> > atomic_set(&fs_info->async_submit_draining, 0);
> > - atomic_set(&fs_info->nr_async_bios, 0);
> > atomic_set(&fs_info->defrag_running, 0);
> > atomic_set(&fs_info->qgroup_op_seq, 0);
> > atomic_set(&fs_info->reada_works_cnt, 0);
> > diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> > index bd679bc..6e9df4d 100644
> > --- a/fs/btrfs/volumes.c
> > +++ b/fs/btrfs/volumes.c
> > @@ -450,13 +450,6 @@ static noinline void run_scheduled_bios(struct btrfs_device *device)
> > pending = pending->bi_next;
> > cur->bi_next = NULL;
> >
> > - /*
> > - * atomic_dec_return implies a barrier for waitqueue_active
> > - */
> > - if (atomic_dec_return(&fs_info->nr_async_bios) < limit &&
>
> And after that the variable 'limit' becomes unused, please remove it as
> well.
>
OK, thanks for the comments.
thanks,
-liubo
> > - waitqueue_active(&fs_info->async_submit_wait))
> > - wake_up(&fs_info->async_submit_wait);
> > -
> > BUG_ON(atomic_read(&cur->__bi_cnt) == 0);
> >
> > /*
> > @@ -6132,13 +6125,6 @@ static noinline void btrfs_schedule_bio(struct btrfs_device *device,
> > return;
> > }
> >
> > - /*
> > - * nr_async_bios allows us to reliably return congestion to the
> > - * higher layers. Otherwise, the async bio makes it appear we have
> > - * made progress against dirty pages when we've really just put it
> > - * on a queue for later
> > - */
> > - atomic_inc(&fs_info->nr_async_bios);
> > WARN_ON(bio->bi_next);
> > bio->bi_next = NULL;
> >
> > --
> > 2.9.4
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-30 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 17:22 [PATCH 0/3] kill async counters Liu Bo
2017-09-07 17:22 ` [PATCH 1/3] Btrfs: remove nr_async_bios Liu Bo
2017-09-27 11:30 ` David Sterba
2017-09-30 1:28 ` Liu Bo [this message]
2017-09-07 17:22 ` [PATCH 2/3] Btrfs: do not make defrag wait on async_delalloc_pages Liu Bo
2017-09-07 17:22 ` [PATCH 3/3] Btrfs: remove nr_async_submits and async_submit_draining Liu Bo
2017-09-27 12:31 ` David Sterba
2017-10-11 17:20 ` David Sterba
2017-10-11 16:49 ` Liu Bo
2017-10-11 18:04 ` 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=20170930012800.GA20449@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).