All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] writeback fixes and cleanups
Date: Wed, 16 Sep 2009 15:31:39 +0200	[thread overview]
Message-ID: <20090916133138.GQ23126@kernel.dk> (raw)
In-Reply-To: <20090915194955.GV23126@kernel.dk>

On Tue, Sep 15 2009, Jens Axboe wrote:
> Hi,
> 
> This should conclude the major updates to the previous writeback
> inclusion, and has a bunch of must have fixes from Nick as well. So I
> think we should include this sooner rather than later, should also fix
> Ingo's bug report.

Linus, JFYI, the diffstat now looks like this:

  git://git.kernel.dk/linux-2.6-block.git writeback

Christoph Hellwig (1):
      writeback: merely wakeup flusher thread if work allocation fails for WB_SYNC_NONE

Jens Axboe (11):
      fs: remove bdev->bd_inode_backing_dev_info
      writeback: get rid of wbc->for_writepages
      writeback: make wb_writeback() take an argument structure
      fs: Assign bdi in super_block
      writeback: only use bdi_writeback_all() for WB_SYNC_NONE writeout
      writeback: use RCU to protect bdi_list
      writeback: inline allocation failure handling in bdi_alloc_queue_work()
      writeback: separate starting of sync vs opportunistic writeback
      writeback: splice dirty inode entries to default bdi on bdi_destroy()
      writeback: add comments to bdi_work structure
      writeback: use schedule_timeout_interruptible()

Nick Piggin (4):
      writeback: remove smp_mb(), it's not needed with list_add_tail_rcu()
      writeback: improve scalability of bdi writeback work queues
      writeback: Fix bdi use after free in wb_work_complete()
      writeback: fix possible bdi writeback refcounting problem

 fs/afs/write.c              |    1 -
 fs/block_dev.c              |    1 -
 fs/btrfs/disk-io.c          |    1 +
 fs/btrfs/ordered-data.c     |    1 -
 fs/fs-writeback.c           |  345 ++++++++++++++++++++-----------------------
 fs/fuse/inode.c             |    2 +
 fs/inode.c                  |    4 +-
 fs/jbd2/commit.c            |    1 -
 fs/nfs/super.c              |    2 +
 fs/nfs/write.c              |    1 -
 fs/nilfs2/the_nilfs.c       |    4 +-
 fs/super.c                  |    6 +
 fs/sync.c                   |    9 +-
 fs/ubifs/budget.c           |   20 +--
 fs/ubifs/super.c            |    1 +
 include/linux/backing-dev.h |    3 +-
 include/linux/fs.h          |    2 +-
 include/linux/writeback.h   |    5 +-
 include/trace/events/ext4.h |    6 +-
 mm/backing-dev.c            |   90 +++++++++---
 mm/page-writeback.c         |   22 +--
 21 files changed, 264 insertions(+), 263 deletions(-)

-- 
Jens Axboe


      reply	other threads:[~2009-09-16 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 19:49 [GIT PULL] writeback fixes and cleanups Jens Axboe
2009-09-16 13:31 ` Jens Axboe [this message]

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=20090916133138.GQ23126@kernel.dk \
    --to=jens.axboe@oracle.com \
    --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 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.