public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Brian Bloniarz <bmb@athenacr.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] block/io bits for 2.6.35-rc
Date: Mon, 28 Jun 2010 16:55:14 -0400	[thread overview]
Message-ID: <4C290C32.4010402@teksavvy.com> (raw)
In-Reply-To: <4C28DCA6.1060503@fusionio.com>

On 28/06/10 01:32 PM, Jens Axboe wrote:
> On 28/06/10 16.05, Brian Bloniarz wrote:
..
>> Links to the patch series that Jens mentions are below. I doubt they
>> apply cleanly to older kernels. Somebody's probably going to need to
>> take a crack at backporting them eventually (I could try, even), but
>> I don't know anybody has yet.
>>
>> Christoph Hellwig (8):
>>        writeback: fix writeback completion notifications
>>        writeback: queue work on stack in writeback_inodes_sb
>>        writeback: enforce s_umount locking in writeback_inodes_sb
>>        writeback: fix writeback_inodes_wb from writeback_inodes_sb
>>        writeback: simplify wakeup_flusher_threads
>>        writeback: simplify and split bdi_start_writeback
>>        writeback: add missing requeue_io in writeback_inodes_wb
>>        writeback: fix pin_sb_for_writeback
>>
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=2c99721ec6a55b2c1e7ba94945bbdae454e11308
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=ebf51611db2cfa33d056b4428f13275f81732fd5
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=de3f848fbc24f71174f3bcc7513b5a3fafb37bac
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=e15e123275b3ca3eeb378136046ab78eab214169
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=dcac2e708d8f8af1a220dd238027af5b4aedfc12
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=8163b53a6bfbfa14ae83f8cdbf536f9c191d3279
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=22e53a2ca88690c711a954d3c652b468a5e94272
>> http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commitdiff;h=7eed7cc254e71352e5e2e642c70a9b04cd28cc76
>
> Yes, that's the series.
..

Those apply/run on 2.6.34 with one minor change to the sixth patch:
Nuke the final one-liner blob from "simplify and split bdi_start_writeback",
getting rid of this part:

--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -705,9 +705,8 @@ void laptop_mode_timer_fn(unsigned long data)
  	 * We want to write everything out, not just down to the dirty
  	 * threshold
  	 */
-
  	if (bdi_has_dirty_io(&q->backing_dev_info))
-		bdi_start_writeback(&q->backing_dev_info, NULL, nr_pages);
+		bdi_start_writeback(&q->backing_dev_info, nr_pages);
  }
  
  /*
----

The rest applied cleanly, and I don't see any obvious need for an alternative
to the deleted line above.

Cheers




  reply	other threads:[~2010-06-28 20:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 13:44 [GIT PULL] block/io bits for 2.6.35-rc Jens Axboe
2010-06-10 15:55 ` Linus Torvalds
2010-06-10 16:25   ` Jens Axboe
2010-06-10 16:40     ` Christoph Hellwig
2010-06-10 16:59       ` Jens Axboe
2010-06-10 17:03       ` Linus Torvalds
2010-06-10 16:44     ` Brian Bloniarz
2010-06-27 23:10       ` Mark Lord
2010-06-28  7:03         ` Jens Axboe
2010-06-28  9:41           ` Christoph Hellwig
2010-06-28 13:51           ` Mark Lord
2010-06-28 14:05             ` Brian Bloniarz
2010-06-28 14:33               ` Mark Lord
2010-06-28 17:32               ` Jens Axboe
2010-06-28 20:55                 ` Mark Lord [this message]
2010-06-10 16:55     ` Linus Torvalds
2010-06-10 17:00       ` Jens Axboe

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=4C290C32.4010402@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=bmb@athenacr.com \
    --cc=hch@lst.de \
    --cc=jaxboe@fusionio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox