linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] writeback for 3.3
Date: Tue, 10 Jan 2012 16:23:58 +0800	[thread overview]
Message-ID: <20120110082358.GA9131@localhost> (raw)

Linus,

Please pull tag 'writeback' from

  git://git.kernel.org/pub/scm/linux/kernel/git/wfg/linux.git writeback-for-linus

They are mostly further improvements to the IO-less balance_dirty_pages().

Jan Kara (1):
      writeback: Include all dirty inodes in background writeback

Wu Fengguang (10):
      writeback: charge leaked page dirties to active tasks
      writeback: fix dirtied pages accounting on sub-page writes
      writeback: fix dirtied pages accounting on redirty
      btrfs: fix dirtied pages accounting on sub-page writes
      writeback: dirty ratelimit - think time compensation
      writeback: max, min and target dirty pause time
      writeback: avoid tiny dirty poll intervals
      writeback: do strict bdi dirty_exceeded
      writeback: balanced_rate cannot exceed write bandwidth
      writeback: move MIN_WRITEBACK_PAGES to fs-writeback.c

 fs/btrfs/file.c                  |    3 +-
 fs/fs-writeback.c                |   16 ++-
 include/linux/sched.h            |    1 +
 include/linux/writeback.h        |    9 +-
 include/trace/events/writeback.h |   14 ++-
 kernel/exit.c                    |    3 +
 kernel/fork.c                    |    1 +
 mm/page-writeback.c              |  246 +++++++++++++++++++++++++++++---------
 8 files changed, 227 insertions(+), 66 deletions(-)

Thanks,
Fengguang

                 reply	other threads:[~2012-01-10  8:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120110082358.GA9131@localhost \
    --to=fengguang.wu@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).