All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Norbert Preining <preining@logic.at>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: dirty throttling v5 for 2.6.37-rc7+
Date: Sat, 25 Dec 2010 15:38:50 +0800	[thread overview]
Message-ID: <20101225073850.GA1626@localhost> (raw)
In-Reply-To: <20101225052736.GA5649@gamma.logic.tuwien.ac.at>

Norbert,

On Sat, Dec 25, 2010 at 01:27:36PM +0800, Norbert Preining wrote:
> Hi Wu,
> 
> merry christmas to everyone!
> 
> > I just created branch "dirty-throttling-v5" based on today's linux-2.6 head.
> 
> Thanks, pulled, built, rebooting.
> 
> I was running v1 for quite some time, without some planned testing.
> Do you want me to do some more planned testing?

> I am running a sony laptop with debian/sid, doing some heavy disk io
> stuff (svn up on *big* repositories).
 
It's already a test to simply run it in your environment, thanks!
Whether it runs fine or not, they will make valuable feedbacks :)

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Norbert Preining <preining@logic.at>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: dirty throttling v5 for 2.6.37-rc7+
Date: Sat, 25 Dec 2010 15:38:50 +0800	[thread overview]
Message-ID: <20101225073850.GA1626@localhost> (raw)
In-Reply-To: <20101225052736.GA5649@gamma.logic.tuwien.ac.at>

Norbert,

On Sat, Dec 25, 2010 at 01:27:36PM +0800, Norbert Preining wrote:
> Hi Wu,
> 
> merry christmas to everyone!
> 
> > I just created branch "dirty-throttling-v5" based on today's linux-2.6 head.
> 
> Thanks, pulled, built, rebooting.
> 
> I was running v1 for quite some time, without some planned testing.
> Do you want me to do some more planned testing?

> I am running a sony laptop with debian/sid, doing some heavy disk io
> stuff (svn up on *big* repositories).
 
It's already a test to simply run it in your environment, thanks!
Whether it runs fine or not, they will make valuable feedbacks :)

Thanks,
Fengguang

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-12-25  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 17:04 dirty throttling v4 for current git kernels Norbert Preining
2010-12-25  3:00 ` dirty throttling v5 for 2.6.37-rc7+ Wu Fengguang
2010-12-25  3:00   ` Wu Fengguang
2010-12-25  5:27   ` Norbert Preining
2010-12-25  5:27     ` Norbert Preining
2010-12-25  7:38     ` Wu Fengguang [this message]
2010-12-25  7:38       ` Wu Fengguang
2011-01-19  4:38       ` Norbert Preining
2011-01-19  4:38         ` Norbert Preining
2011-01-20 13:39         ` Wu Fengguang

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=20101225073850.GA1626@localhost \
    --to=fengguang.wu@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=preining@logic.at \
    /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.