From: Mel Gorman <mgorman@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jerome Marchand <jmarchan@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm: swap: Mark swap pages writeback before queueing for direct IO
Date: Thu, 25 Apr 2013 09:53:51 +0100 [thread overview]
Message-ID: <20130425085350.GC2144@suse.de> (raw)
In-Reply-To: <20130424122313.381167c5ad702fc991844bc7@linux-foundation.org>
On Wed, Apr 24, 2013 at 12:23:13PM -0700, Andrew Morton wrote:
> > } else {
> > + /*
> > + * In the case of swap-over-nfs, this can be a
> > + * temporary failure if the system has limited
> > + * memory for allocating transmit buffers.
> > + * Mark the page dirty and avoid
> > + * rotate_reclaimable_page but rate-limit the
> > + * messages but do not flag PageError like
> > + * the normal direct-to-bio case as it could
> > + * be temporary.
> > + */
> > set_page_dirty(page);
> > + ClearPageReclaim(page);
> > + if (printk_ratelimit()) {
> > + pr_err("Write-error on dio swapfile (%Lu)\n",
> > + (unsigned long long)page_file_offset(page));
> > + }
> > }
> > + end_page_writeback(page);
>
> A pox upon printk_ratelimit()! Both its code comment and the
> checkpatch warning explain why.
>
Ok. There were few sensible options around dealing with the write
errors. swap_writepage() could go to sleep on a waitqueue but it's
putting IO rate limiting where it doesn't belong. Retrying silently
forever could be difficult to debug if the error really is permanent.
> --- a/mm/page_io.c~mm-swap-mark-swap-pages-writeback-before-queueing-for-direct-io-fix
> +++ a/mm/page_io.c
> @@ -244,10 +244,8 @@ int __swap_writepage(struct page *page,
> */
> set_page_dirty(page);
> ClearPageReclaim(page);
> - if (printk_ratelimit()) {
> - pr_err("Write-error on dio swapfile (%Lu)\n",
> - (unsigned long long)page_file_offset(page));
> - }
> + pr_err_ratelimited("Write error on dio swapfile (%Lu)\n",
> + (unsigned long long)page_file_offset(page));
> }
> end_page_writeback(page);
> return ret;
>
> Do we need to cast the loff_t? afaict all architectures use long long.
> I didn't get a warning from sparc64 with the cast removed, and sparc64
> is the one which likes to use different underlying types.
>
> I think I'll remove it and wait for Fengguang's nastygram.
>
Sounds reasonable. I'll get cc'd on the same mails.
--
Mel Gorman
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:[~2013-04-25 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 12:11 [PATCH] swap: redirty page if page write fails on swap file Jerome Marchand
2013-04-17 15:07 ` Johannes Weiner
2013-04-17 15:08 ` Mel Gorman
2013-04-18 0:13 ` Simon Jeons
2013-05-01 7:39 ` Simon Jeons
2013-05-03 9:12 ` Jerome Marchand
2013-04-22 20:37 ` Andrew Morton
2013-04-24 9:57 ` Jerome Marchand
2013-05-01 7:38 ` Will Huck
2013-04-24 18:57 ` [PATCH] mm: swap: Mark swap pages writeback before queueing for direct IO Mel Gorman
2013-04-24 19:23 ` Andrew Morton
2013-04-25 8:53 ` Mel Gorman [this message]
2013-05-01 6:58 ` Ric Mason
2013-05-01 8:20 ` Mel Gorman
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=20130425085350.GC2144@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).