From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: linux-btrfs@vger.kernel.org, sekharan@us.ibm.com,
chris.mason@fusionio.com, Ilya Dryomov <idryomov@gmail.com>,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: Re: [RFC 0/5] BTRFS hot relocation support
Date: Thu, 09 May 2013 09:41:46 +0200 [thread overview]
Message-ID: <518B533A.7020503@giantdisaster.de> (raw)
In-Reply-To: <CAEH94LiBzA0SEg+TKRs8_MP43UEDq6ULU2WfjYmAMhneHRZKpw@mail.gmail.com>
On 05/09/2013 08:42, Zhi Yong Wu wrote:
> btrfs maintainer's opinion is very important, i guess.
My opinion is not important and I shall shut up?
> On Thu, May 9, 2013 at 2:30 PM, Stefan Behrens
> <sbehrens@giantdisaster.de> wrote:
>> On 05/09/2013 01:13, Zhi Yong Wu wrote:
>>>
>>> HI, all
>>>
>>> I saw that bcache will be merged into kernel upstream soon, so i
>>> want to know if btrfs hot relocation support is still meanful, if no,
>>> i will not continue to work on it. can anyone let me know this?
>>> thanks.
>>
>>
>> Which one is better?
>>
>> Please do some measurements. Select typical file system use cases, and
>> publish and compare the measurement results of the two approaches.
next prev parent reply other threads:[~2013-05-09 7:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 8:53 [RFC 0/5] BTRFS hot relocation support zwu.kernel
2013-05-06 8:53 ` [RFC 1/5] vfs: add one list_head field zwu.kernel
2013-05-06 8:53 ` [RFC 2/5] btrfs: add one new block group zwu.kernel
2013-05-06 8:53 ` [RFC 3/5] btrfs: add one hot relocation kthread zwu.kernel
2013-05-06 8:53 ` [RFC 4/5] procfs: add three proc interfaces zwu.kernel
2013-05-06 8:53 ` [RFC 5/5] btrfs: add hot relocation support zwu.kernel
2013-05-06 20:36 ` [RFC 0/5] BTRFS " Kai Krakow
2013-05-07 5:17 ` Tomasz Torcz
2013-05-07 21:17 ` Kai Krakow
2013-05-07 21:35 ` Gabriel de Perthuis
2013-05-07 21:58 ` Kai Krakow
2013-05-07 22:27 ` Gabriel de Perthuis
2013-05-08 23:13 ` Zhi Yong Wu
2013-05-09 6:30 ` Stefan Behrens
2013-05-09 6:42 ` Zhi Yong Wu
2013-05-09 7:41 ` Stefan Behrens [this message]
2013-05-09 7:49 ` Zhi Yong Wu
2013-05-09 7:28 ` Zheng Liu
2013-05-09 6:56 ` Roger Binns
2013-05-19 10:41 ` Martin Steigerwald
2013-05-19 13:43 ` Zhi Yong Wu
2013-05-19 14:42 ` Martin Steigerwald
2013-05-19 13:46 ` Zhi Yong Wu
2013-05-09 7:17 ` Gabriel de Perthuis
2013-05-14 15:24 ` Zhi Yong Wu
2013-05-16 7:12 ` Kai Krakow
2013-05-17 7:23 ` Zhi Yong Wu
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=518B533A.7020503@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=chris.mason@fusionio.com \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sekharan@us.ibm.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.com \
/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