From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [PATCH 3/5] mm: Implement IO-less balance_dirty_pages()
Date: Fri, 04 Feb 2011 14:09:16 +0100 [thread overview]
Message-ID: <1296824956.26581.650.camel@laptop> (raw)
In-Reply-To: <1296783534-11585-4-git-send-email-jack@suse.cz>
On Fri, 2011-02-04 at 02:38 +0100, Jan Kara wrote:
> +static int check_dirty_limits(struct backing_dev_info *bdi,
> + struct dirty_limit_state *pst)
> +{
> + struct dirty_limit_state st;
> + unsigned long bdi_thresh;
> + unsigned long min_bdi_thresh;
> + int ret = DIRTY_OK;
>
> + get_global_dirty_limit_state(&st);
> + /*
> + * Throttle it only when the background writeback cannot catch-up. This
> + * avoids (excessively) small writeouts when the bdi limits are ramping
> + * up.
> + */
> + if (st.nr_reclaimable + st.nr_writeback <=
> + (st.background_thresh + st.dirty_thresh) / 2)
> + goto out;
>
> + get_bdi_dirty_limit_state(bdi, &st);
> + min_bdi_thresh = task_min_dirty_limit(st.bdi_thresh);
> + bdi_thresh = task_dirty_limit(current, st.bdi_thresh);
> +
> + /*
> + * The bdi thresh is somehow "soft" limit derived from the global
> + * "hard" limit. The former helps to prevent heavy IO bdi or process
> + * from holding back light ones; The latter is the last resort
> + * safeguard.
> + */
> + if ((st.bdi_nr_reclaimable + st.bdi_nr_writeback > bdi_thresh)
> + || (st.nr_reclaimable + st.nr_writeback > st.dirty_thresh)) {
> + ret = DIRTY_EXCEED_LIMIT;
> + goto out;
> + }
> + if (st.bdi_nr_reclaimable + st.bdi_nr_writeback > min_bdi_thresh) {
> + ret = DIRTY_MAY_EXCEED_LIMIT;
> + goto out;
> + }
> + if (st.nr_reclaimable > st.background_thresh)
> + ret = DIRTY_EXCEED_BACKGROUND;
> +out:
> + if (pst)
> + *pst = st;
By mandating pst is always provided you can reduce the total stack
footprint, avoid the memcopy and clean up the control flow ;-)
> + return ret;
> +}
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-04 13:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 1:38 [RFC PATCH 0/5] IO-less balance dirty pages Jan Kara
2011-02-04 1:38 ` [PATCH 1/5] writeback: account per-bdi accumulated written pages Jan Kara
2011-02-04 1:38 ` [PATCH 2/5] mm: Properly reflect task dirty limits in dirty_exceeded logic Jan Kara
2011-02-04 1:38 ` [PATCH 3/5] mm: Implement IO-less balance_dirty_pages() Jan Kara
2011-02-04 13:09 ` Peter Zijlstra
2011-02-11 14:56 ` Jan Kara
2011-02-04 13:09 ` Peter Zijlstra [this message]
2011-02-11 14:56 ` Jan Kara
2011-02-04 13:09 ` Peter Zijlstra
2011-02-04 13:19 ` Peter Zijlstra
2011-02-11 15:46 ` Jan Kara
2011-02-22 15:40 ` Peter Zijlstra
2011-02-04 1:38 ` [PATCH 4/5] mm: Remove low limit from sync_writeback_pages() Jan Kara
2011-02-04 1:38 ` [PATCH 5/5] mm: Autotune interval between distribution of page completions Jan Kara
2011-02-04 13:09 ` Peter Zijlstra
2011-02-11 15:49 ` Jan Kara
2011-02-06 17:54 ` [RFC PATCH 0/5] IO-less balance dirty pages Boaz Harrosh
2011-02-09 23:30 ` Jan Kara
2011-02-10 12:08 ` Boaz Harrosh
-- strict thread matches above, loose matches on Subject: below --
2011-03-08 22:31 [PATCH RFC 0/5] IO-less balance_dirty_pages() v2 (simple approach) Jan Kara
2011-03-08 22:31 ` [PATCH 3/5] mm: Implement IO-less balance_dirty_pages() Jan Kara
2011-03-10 0:07 ` Vivek Goyal
2011-03-14 20:48 ` Jan Kara
2011-03-15 15:23 ` Vivek Goyal
2011-03-16 21:26 ` Curt Wohlgemuth
2011-03-16 22:53 ` Curt Wohlgemuth
2011-03-16 16:53 ` Vivek Goyal
2011-03-16 19:10 ` Jan Kara
2011-03-16 19:31 ` Vivek Goyal
2011-03-16 19:58 ` Jan Kara
2011-03-16 20:22 ` Vivek Goyal
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=1296824956.26581.650.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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).