All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Fengguang Wu <wfg@mail.ustc.edu.cn>,
	David <david@unsolicited.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 2.6.24-rc1 - Regularly getting processes stuck in D state on startup
Date: Mon, 12 Nov 2007 21:29:05 -0800	[thread overview]
Message-ID: <20071112212905.abdf6078.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071113161145.6433e1c1.sfr@canb.auug.org.au>

On Tue, 13 Nov 2007 16:11:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> On Wed, 7 Nov 2007 14:46:47 +0800 Fengguang Wu <wfg@mail.ustc.edu.cn> wrote:
> >
> > Thank you(including David:-)) for the confirmation.
> > 
> > Andrew: so mm-speed-up-writeback-ramp-up-on-clean-systems.patch is a
> > safe and working patch ;-)
> 
> So is anything happening with this patch?  It is really necessary to have
> it (or something equivalent) in 2.6.24.
> 

It's in my queue of 2.6.24 stuff.  Along with, umm, 112 other patches.

      reply	other threads:[~2007-11-13  5:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 18:23 2.6.24-rc1 - Regularly getting processes stuck in D state on startup David
2007-11-06  6:46 ` Stephen Rothwell
2007-11-06 12:20   ` Peter Zijlstra
2007-11-07  3:24   ` Stephen Rothwell
2007-11-06  8:00 ` Fengguang Wu
2007-11-06  8:00   ` Fengguang Wu
2007-11-06 18:03     ` David
2007-11-06  8:21   ` Fengguang Wu
2007-11-06  8:21     ` Fengguang Wu
2007-11-07  3:17       ` Stephen Rothwell
2007-11-07  3:26         ` Stephen Rothwell
2007-11-07  6:46           ` Fengguang Wu
2007-11-07  6:46             ` Fengguang Wu
2007-11-13  5:11               ` Stephen Rothwell
2007-11-13  5:29                 ` Andrew Morton [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=20071112212905.abdf6078.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=david@unsolicited.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wfg@mail.ustc.edu.cn \
    /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.