From: harshad shirwadkar <harshadshirwadkar@gmail.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Cc: Liu Bo <bo.li.liu@oracle.com>
Subject: Re: [GSoC 2015] Btrfs content based storage
Date: Tue, 14 Apr 2015 11:21:49 -0400 [thread overview]
Message-ID: <CAD+ocbwDR+be-Lf6LmZGrUhVA5D5Ds2q9LV=6xXgdPZ3tfQs4A@mail.gmail.com> (raw)
In-Reply-To: <20150413144743.GL25622@twin.jikos.cz>
Thanks David and that's true: there will be a large overlap with dedup
work from Liu Bo. In fact, a few days after I sent the first mail, I
got in touch with Liu and he agreed upon mentoring. So, I am all set
now and will start working on the project in May end..
Best,
Harshad.
On Mon, Apr 13, 2015 at 10:47 AM, David Sterba <dsterba@suse.cz> wrote:
> On Fri, Mar 27, 2015 at 10:58:42AM -0400, harshad shirwadkar wrote:
>> I am a CS graduate student from Carnegie Mellon University. I am
>> hoping to build the feature - "Content based storage mode" under
>> Google Summer of Code 2015. This project has also been listed as an
>> idea on BTRFS ideas page. However, I have not found a mentor yet, and
>> without a mentor I can not participate in the program. Please let me
>> know if anybody is interested in mentoring this project. Here is a
>> link to my proposal:
>>
>> http://harshadjs.github.io/2015/03/27/Fedora-BTRFS-Content-Storage-Mode/
>
> This probably has a significant overlap with the in-band dedup work from
> Liu bo [1]. Your proposal expects an interface to look up the data by
> hash which hasn't been implemented afaik.
>
> [1] http://thread.gmane.org/gmane.comp.file-systems.btrfs/34097 (v10)
prev parent reply other threads:[~2015-04-14 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:58 [GSoC 2015] Btrfs content based storage harshad shirwadkar
2015-04-13 14:47 ` David Sterba
2015-04-14 15:21 ` harshad shirwadkar [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='CAD+ocbwDR+be-Lf6LmZGrUhVA5D5Ds2q9LV=6xXgdPZ3tfQs4A@mail.gmail.com' \
--to=harshadshirwadkar@gmail.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).