From: Michal Hocko <mhocko@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
tj@kernel.org
Subject: Re: [PATCH] writeback: Avoid exhausting allocation reserves under memory pressure
Date: Thu, 5 May 2016 10:24:33 +0200 [thread overview]
Message-ID: <20160505082433.GC4386@dhcp22.suse.cz> (raw)
In-Reply-To: <1462436092-32665-1-git-send-email-jack@suse.cz>
On Thu 05-05-16 10:14:52, Jan Kara wrote:
> When system is under memory pressure memory management frequently calls
> wakeup_flusher_threads() to writeback pages to that they can be freed.
> This was observed to exhaust reserves for atomic allocations since
> wakeup_flusher_threads() allocates one writeback work for each device
> with dirty data with GFP_ATOMIC.
>
> However it is pointless to allocate new work items when requested work
> is identical. Instead, we can merge the new work with the pending work
> items and thus save memory allocation.
Makes sense. See one question below:
> Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/fs-writeback.c | 37 +++++++++++++++++++++++++++++++++++++
> include/trace/events/writeback.h | 1 +
> 2 files changed, 38 insertions(+)
>
> This is a patch which should (and in my basic testing does) address the issues
> with many atomic allocations Tetsuo reported. What do people think?
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index fee81e8768c9..bb6725f5b1ba 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -189,6 +189,35 @@ out_unlock:
> spin_unlock_bh(&wb->work_lock);
> }
>
> +/*
> + * Check whether the request to writeback some pages can be merged with some
> + * other request which is already pending. If yes, merge it and return true.
> + * If no, return false.
> + */
> +static bool wb_merge_request(struct bdi_writeback *wb, long nr_pages,
> + struct super_block *sb, bool range_cyclic,
> + enum wb_reason reason)
> +{
> + struct wb_writeback_work *work;
> + bool merged = false;
> +
> + spin_lock_bh(&wb->work_lock);
> + list_for_each_entry(work, &wb->work_list, list) {
Is the lenght of the list bounded somehow? In other words is it possible
that the spinlock would be held for too long to traverse the whole list?
> + if (work->reason == reason &&
> + work->range_cyclic == range_cyclic &&
> + work->auto_free == 1 && work->sb == sb &&
> + work->for_sync == 0) {
> + work->nr_pages += nr_pages;
> + merged = true;
> + trace_writeback_merged(wb, work);
> + break;
> + }
> + }
> + spin_unlock_bh(&wb->work_lock);
> +
> + return merged;
> +}
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-05 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 8:14 [PATCH] writeback: Avoid exhausting allocation reserves under memory pressure Jan Kara
2016-05-05 8:24 ` Michal Hocko [this message]
2016-05-05 9:07 ` Jan Kara
2016-05-05 9:18 ` Michal Hocko
2016-05-05 21:37 ` Andrew Morton
2016-05-12 16:08 ` Jan Kara
2016-05-16 11:45 ` Michal Hocko
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=20160505082433.GC4386@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tj@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 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.