Prev: [RFC] Multiboot2 drafting
Next: Ptrace : reading process user area, stack size etc
From: Matthew Garrett on 3 Apr 2010 13:20
On Tue, Dec 15, 2009 at 01:21:35PM -0500, Matthew Garrett wrote:
> One of the features of laptop-mode is that it forces a writeout of dirty
> pages if something else triggers a physical read or write from a device.
> The current implementation flushes pages on all devices, rather than only
> the one that triggered the flush. This patch alters the behaviour so that
> only the recently accessed block device is flushed, preventing other
> disks being spun up for no terribly good reason.

Hi Jens,

Can you remember if there were any more issues with this, or can this
version be merged now?

Thanks,
--
Matthew Garrett | mjg59(a)srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jens Axboe on 6 Apr 2010 08:30
On Sat, Apr 03 2010, Matthew Garrett wrote:
> On Tue, Dec 15, 2009 at 01:21:35PM -0500, Matthew Garrett wrote:
> > One of the features of laptop-mode is that it forces a writeout of dirty
> > pages if something else triggers a physical read or write from a device.
> > The current implementation flushes pages on all devices, rather than only
> > the one that triggered the flush. This patch alters the behaviour so that
> > only the recently accessed block device is flushed, preventing other
> > disks being spun up for no terribly good reason.
>
> Hi Jens,
>
> Can you remember if there were any more issues with this, or can this
> version be merged now?

I think it's fine to merge, I'll queue it up for 2.6.35.

--
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [RFC] Multiboot2 drafting
Next: Ptrace : reading process user area, stack size etc