From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/5 v3] xfs: get rid of xfs_cluster_write()
Date: Mon, 8 Feb 2016 16:44:13 +1100 [thread overview]
Message-ID: <1454910258-7578-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
Still clearing out my pending patches. This one was last posted
almost 6 months ago:
http://oss.sgi.com/archives/xfs/2015-08/msg00523.html
The main issue at the time was the fact that the ioends were added
to the writepage context and only submitted once
write_cached_pages() was done, resulting in building up a large
number of writeback pages and allocated ioends before IO submission
was done. hence we could potentially prevent writeback progress from
being made due to mempool starvation as we weren't following the
required rules for the ioend mempool.
This is addressed in the new patch 5. instead of chaining ioends
onto the writepage context, we submit completed ioends the moment we
are done processing the page that triggered allocation of a new
ioend. Hence we issue ioends as they are built, rather than as a
batch once page processing is done. This ensures that writeback
follows the rules required for mempools to work effectively and we
won't deadlock due to mempool starvation during low memory
writeback.
This modified patch set has been sitting in my queue now for almost
4 months, so it's time to get it moved onwards...
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-08 5:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 5:44 Dave Chinner [this message]
2016-02-08 5:44 ` [PATCH 1/5] xfs: remove nonblocking mode from xfs_vm_writepage Dave Chinner
2016-02-08 5:44 ` [PATCH 2/5] xfs: Introduce writeback context for writepages Dave Chinner
2016-02-09 13:39 ` Christoph Hellwig
2016-02-09 21:48 ` Dave Chinner
2016-02-09 23:16 ` Dave Chinner
2016-02-09 14:22 ` Brian Foster
2016-02-09 21:51 ` Dave Chinner
2016-02-08 5:44 ` [PATCH 3/5] xfs: xfs_cluster_write is redundant Dave Chinner
2016-02-09 13:40 ` Christoph Hellwig
2016-02-08 5:44 ` [PATCH 4/5] xfs: factor mapping out of xfs_do_writepage Dave Chinner
2016-02-09 13:40 ` Christoph Hellwig
2016-02-08 5:44 ` [PATCH 5/5] xfs: don't chain ioends during writepage submission Dave Chinner
2016-02-09 13:49 ` Christoph Hellwig
2016-02-09 21:52 ` Dave Chinner
2016-02-09 14:23 ` Brian Foster
2016-02-09 21:59 ` Dave Chinner
2016-02-10 13:18 ` Brian Foster
2016-02-10 21:09 ` Dave Chinner
2016-02-11 12:24 ` Brian Foster
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=1454910258-7578-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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