From: Jan Kara <jack@suse.cz>
To: Brian Foster <bfoster@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, Petr Tuma <petr.tuma@d3s.mff.cuni.cz>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] xfs: Timely free truncated dirty pages
Date: Wed, 11 Jan 2017 09:57:28 +0100 [thread overview]
Message-ID: <20170111085728.GC16116@quack2.suse.cz> (raw)
In-Reply-To: <20170110124320.GA3321@bfoster.bfoster>
On Tue 10-01-17 07:43:20, Brian Foster wrote:
> On Tue, Jan 10, 2017 at 11:17:45AM +0100, Jan Kara wrote:
> > Commit 99579ccec4e2 "xfs: skip dirty pages in ->releasepage()" started
> > to skip dirty pages in xfs_vm_releasepage() which also has the effect
> > that if a dirty page is truncated, it does not get freed by
> > block_invalidatepage() and is lingering in LRU list waiting for reclaim.
> > So a simple loop like:
> >
> > while true; do
> > dd if=/dev/zero of=file bs=1M count=100
> > rm file
> > done
> >
> > will keep using more and more memory until we hit low watermarks and
> > start pagecache reclaim which will eventually reclaim also the truncate
> > pages. Keeping these truncated (and thus never usable) pages in memory
> > is just a waste of memory, is unnecessarily stressing page cache
> > reclaim, and is also confusing users thinking they are running out of
> > memory.
> >
> > So instead of just skipping dirty pages in xfs_vm_releasepage(), return
> > to old behavior of skipping them only if they have delalloc or unwritten
> > buffers and fix the spurious warnings by warning only if the page is
> > clean.
> >
> > CC: Brian Foster <bfoster@redhat.com>
> > CC: Vlastimil Babka <vbabka@suse.cz>
> > Reported-by: Petr Tůma <petr.tuma@d3s.mff.cuni.cz>
> > Fixes: 99579ccec4e271c3d4d4e7c946058766812afdab
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
>
> Ugh, so this is closer to the alternative I was considering at the time
> this was posted. Thanks for the fix. The code looks fine, I'd just like
> to update the comment...
OK, done.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-01-11 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 10:17 [PATCH] xfs: Timely free truncated dirty pages Jan Kara
2017-01-10 11:09 ` Vlastimil Babka
2017-01-10 12:43 ` Brian Foster
2017-01-11 8:57 ` Jan Kara [this message]
2017-01-11 8:07 ` Vlastimil Babka
2017-01-11 8:19 ` Vlastimil Babka
2017-01-11 8:59 ` Jan Kara
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=20170111085728.GC16116@quack2.suse.cz \
--to=jack@suse.cz \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=petr.tuma@d3s.mff.cuni.cz \
--cc=vbabka@suse.cz \
/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.