Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1615923
| From | Michal Hocko <mhocko@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. |
| Date | 2017-04-04 13:30 +0200 |
| Message-ID | <tsuOR-4cn-13@gated-at.bofh.it> (permalink) |
| References | <trYOZ-8pQ-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 03-04-17 11:18:51, NeilBrown wrote:
>
> When a filesystem is mounted from a loop device, writes are
> throttled by balance_dirty_pages() twice: once when writing
> to the filesystem and once when the loop_handle_cmd() writes
> to the backing file. This double-throttling can trigger
> positive feedback loops that create significant delays. The
> throttling at the lower level is seen by the upper level as
> a slow device, so it throttles extra hard.
>
> The PF_LESS_THROTTLE flag was created to handle exactly this
> circumstance, though with an NFS filesystem mounted from a
> local NFS server. It reduces the throttling on the lower
> layer so that it can proceed largely unthrottled.
>
> To demonstrate this, create a filesystem on a loop device
> and write (e.g. with dd) several large files which combine
> to consume significantly more than the limit set by
> /proc/sys/vm/dirty_ratio or dirty_bytes. Measure the total
> time taken.
>
> When I do this directly on a device (no loop device) the
> total time for several runs (mkfs, mount, write 200 files,
> umount) is fairly stable: 28-35 seconds.
> When I do this over a loop device the times are much worse
> and less stable. 52-460 seconds. Half below 100seconds,
> half above.
> When I apply this patch, the times become stable again,
> though not as fast as the no-loop-back case: 53-72 seconds.
>
> There may be room for further improvement as the total overhead still
> seems too high, but this is a big improvement.
Yes this makes sense to me
> Signed-off-by: NeilBrown <neilb@suse.com>
Acked-by: Michal Hocko <mhocko@suse.com>
one nit below
> ---
> drivers/block/loop.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index 0ecb6461ed81..a7e1dd215fc2 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -1694,8 +1694,11 @@ static void loop_queue_work(struct kthread_work *work)
> {
> struct loop_cmd *cmd =
> container_of(work, struct loop_cmd, work);
> + int oldflags = current->flags & PF_LESS_THROTTLE;
>
> + current->flags |= PF_LESS_THROTTLE;
> loop_handle_cmd(cmd);
> + current->flags = (current->flags & ~PF_LESS_THROTTLE) | oldflags;
we have a helper for this tsk_restore_flags(). It is not used
consistently and maybe we want a dedicated api like we have for the
scope NOIO/NOFS but that is a separate thing. I would find
tsk_restore_flags easier to read.
--
Michal Hocko
SUSE Labs
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-03 03:20 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. Christoph Hellwig <hch@infradead.org> - 2017-04-04 09:20 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-05 06:30 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. Ming Lei <tom.leiming@gmail.com> - 2017-04-05 07:20 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. Michal Hocko <mhocko@kernel.org> - 2017-04-04 13:30 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. Ming Lei <tom.leiming@gmail.com> - 2017-04-04 16:30 +0200
Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-05 06:40 +0200
[PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-05 06:40 +0200
Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. Ming Lei <tom.leiming@gmail.com> - 2017-04-05 07:10 +0200
Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. Michal Hocko <mhocko@kernel.org> - 2017-04-05 09:20 +0200
Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. Michal Hocko <mhocko@kernel.org> - 2017-04-05 09:40 +0200
Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-06 04:30 +0200
Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread. Michal Hocko <mhocko@kernel.org> - 2017-04-06 09:00 +0200
[PATCH v3] loop: Add PF_LESS_THROTTLE to block/loop device thread. NeilBrown <neilb@suse.com> - 2017-04-07 01:50 +0200
csiph-web