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: dirty throttling v5 for 2.6.37-rc7+
Date: Sat, 25 Dec 2010 11:00:19 +0800 [thread overview]
Message-ID: <20101225030019.GA25383@localhost> (raw)
In-Reply-To: <20101224170418.GA3405@gamma.logic.tuwien.ac.at>
Hi Norbert,
Merry Christmas! :)
On Sat, Dec 25, 2010 at 01:04:18AM +0800, Norbert Preining wrote:
> Hi Wu, hi everyone,
>
> (pleae Cc)
>
> is there any chance to get a git pull-able repository of the
> IO-less dirty throttling v4
> patches (git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git dirty-throttling-v4) for usage with current git kernel? There are several
> rejects if I try to merge them into the current linux-2.6 head.
I just created branch "dirty-throttling-v5" based on today's linux-2.6 head.
git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git dirty-throttling-v5
The test scripts are also updated at
http://www.kernel.org/pub/linux/kernel/people/wfg/writeback/tests/
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: dirty throttling v5 for 2.6.37-rc7+
Date: Sat, 25 Dec 2010 11:00:19 +0800 [thread overview]
Message-ID: <20101225030019.GA25383@localhost> (raw)
In-Reply-To: <20101224170418.GA3405@gamma.logic.tuwien.ac.at>
Hi Norbert,
Merry Christmas! :)
On Sat, Dec 25, 2010 at 01:04:18AM +0800, Norbert Preining wrote:
> Hi Wu, hi everyone,
>
> (pleae Cc)
>
> is there any chance to get a git pull-able repository of the
> IO-less dirty throttling v4
> patches (git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git dirty-throttling-v4) for usage with current git kernel? There are several
> rejects if I try to merge them into the current linux-2.6 head.
I just created branch "dirty-throttling-v5" based on today's linux-2.6 head.
git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git dirty-throttling-v5
The test scripts are also updated at
http://www.kernel.org/pub/linux/kernel/people/wfg/writeback/tests/
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>
next prev parent reply other threads:[~2010-12-25 3:00 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 ` Wu Fengguang [this message]
2010-12-25 3:00 ` dirty throttling v5 for 2.6.37-rc7+ Wu Fengguang
2010-12-25 5:27 ` Norbert Preining
2010-12-25 5:27 ` Norbert Preining
2010-12-25 7:38 ` Wu Fengguang
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=20101225030019.GA25383@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.