From: "Matias Bjørling" <mabj@itu.dk>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: <jmad@itu.dk>, <linux-btrfs@vger.kernel.org>,
<chris.mason@fusionio.com>, <dsterba@suse.cz>
Subject: Re: [POSSIBLE SPAM] Re: Hybrid Storage proposal
Date: Tue, 26 Feb 2013 14:08:52 +0100 [thread overview]
Message-ID: <512CB3E4.9040203@itu.dk> (raw)
In-Reply-To: <CAEH94Liiy3ftSrkpiKyr68LHwQw55od4LY6hzZwzBKtCixxg+w@mail.gmail.com>
On 02/26/2013 12:04 PM, Zhi Yong Wu wrote:
> HI,
>
> It's a bit long so that i haven't read its whole, but i want to know
> if it has any collision with my ongoing feature "btrfs hot
> relocation/migration"?
It will utilize the hot track patch set you're been creating for VFS. I
think the methods are complementary. Do you have a description of the
relocation/migration approach?
next prev parent reply other threads:[~2013-02-26 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 16:46 Hybrid Storage proposal Matias Bjorling
2013-02-20 19:19 ` Alex Elsayed
2013-02-21 9:25 ` Matias Bjørling
2013-02-21 0:49 ` Gareth Pye
2013-02-21 6:53 ` Alex Elsayed
2013-02-26 11:04 ` Zhi Yong Wu
2013-02-26 13:08 ` Matias Bjørling [this message]
2013-02-27 11:50 ` [POSSIBLE SPAM] " 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=512CB3E4.9040203@itu.dk \
--to=mabj@itu.dk \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=jmad@itu.dk \
--cc=linux-btrfs@vger.kernel.org \
--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