All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Stapelberg <stapelberg+linux@google.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org,  linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 0/5] writeback: Fix bandwidth estimates
Date: Tue, 13 Jul 2021 10:15:33 +0200	[thread overview]
Message-ID: <CAH9Oa-b9DT78Thja1QHTUk3jQTD5A0kbzRGM6b2SBjPdd5Mehg@mail.gmail.com> (raw)
In-Reply-To: <20210712162733.GB9804@quack2.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

Yes! Thank you.

On Mon, 12 Jul 2021 at 18:27, Jan Kara <jack@suse.cz> wrote:

> On Fri 09-07-21 15:19:17, Michael Stapelberg wrote:
> > Thanks for sending this patch series!
> >
> > I have used the mmap.c reproducer as before, with the following
> parameters:
> > * mkdir /tmp/mnt
> > * fusermount -u /tmp/mnt; /root/fuse-2.9.9/example/fusexmp_fh -f /tmp/mnt
> > * dd if=/dev/urandom of=/tmp/was bs=1M count=99
> > * while :; do grep ^Bdi /sys/kernel/debug/bdi/0:44/stats; sleep 0.1; done
> > * while :; do time WORKAROUND=1 ~/mmap /tmp/was
> > /tmp/mnt/tmp/stapelberg.1; sleep 5; done
> >
> > Previously, after a few iterations, the BdiWriteBandwidth measure
> > would gradually approach 0.
> >
> > With your patch series applied, the BdiWriteBandwidth is updated much
> > more quickly, and converges to ≈16000 kBps.
> > When I start copying more quickly, the bandwidth measure rises quickly.
> >
> > As far as I understand, this should fix the problem (provided 16000
> > kBps is an okay value).
> > Certainly, I don’t see the downward spiral either with your patches :)
>
> Thanks for testing! Can I add your Tested-by tag?
>
>                                                                 Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>

[-- Attachment #2: Type: text/html, Size: 1764 bytes --]

      reply	other threads:[~2021-07-13  8:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 16:23 [PATCH 0/5] writeback: Fix bandwidth estimates Jan Kara
2021-07-05 16:23 ` [PATCH 1/5] writeback: Track number of inodes under writeback Jan Kara
2021-07-05 16:23 ` [PATCH 2/5] writeback: Reliably update bandwidth estimation Jan Kara
2021-07-05 16:23 ` [PATCH 3/5] writeback: Fix bandwidth estimate for spiky workload Jan Kara
2021-07-07  7:40   ` Hillf Danton
2021-07-07  9:51     ` Jan Kara
2021-07-08 12:17       ` Hillf Danton
2021-07-08 16:43         ` Jan Kara
2021-07-09  8:01           ` Hillf Danton
2021-07-05 16:23 ` [PATCH 4/5] writeback: Rename domain_update_bandwidth() Jan Kara
2021-07-05 16:23 ` [PATCH 5/5] writeback: Use READ_ONCE for unlocked reads of writeback stats Jan Kara
2021-07-09 13:19 ` [PATCH 0/5] writeback: Fix bandwidth estimates Michael Stapelberg
2021-07-09 13:19   ` Michael Stapelberg
2021-07-12 16:27   ` Jan Kara
2021-07-13  8:15     ` Michael Stapelberg [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=CAH9Oa-b9DT78Thja1QHTUk3jQTD5A0kbzRGM6b2SBjPdd5Mehg@mail.gmail.com \
    --to=stapelberg+linux@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.