From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Vimal A R <arvimal@yahoo.in>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas for a feature implementation
Date: Sun, 10 Aug 2014 22:53:41 -0400 [thread overview]
Message-ID: <53E83035.8010603@gmail.com> (raw)
In-Reply-To: <1407698476.20187.YahooMailNeo@web192906.mail.sg3.yahoo.com>
On 08/10/2014 03:21 PM, Vimal A R wrote:
> Hello,
>
> I came across the to-do list at https://btrfs.wiki.kernel.org/index.php/Project_ideas and would like to know if this list is updated and recent.
>
> I am looking for a project idea for my under graduate degree which can be completed in around 3-4 months. Are there any suggestions and ideas to help me further?
>
> Thank you,
> Vimal
It's not really listed there (though some of the projects there might be
considered subsets of it), but improved parallelization for the
multi-device setups is one thing that I know that a lot of people would
like to see.
Another thing that isn't listed there, that I would personally love to
see is support for secure file deletion. To be truly secure though,
this would need to hook into the COW logic so that files marked for
secure deletion can't be reflinked (maybe make the automatically NOCOW
instead, and don't allow snapshots?), and when they get written to, the
blocks that get COW'ed have the old block overwritten.
next prev parent reply other threads:[~2014-08-11 2:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 19:21 Ideas for a feature implementation Vimal A R
2014-08-11 2:53 ` Austin S Hemmelgarn [this message]
2014-08-11 20:27 ` Chris Murphy
2014-08-12 2:27 ` Austin S Hemmelgarn
2014-08-12 3:04 ` Chris Murphy
2014-08-12 15:52 ` David Pottage
2014-08-12 17:34 ` Austin S Hemmelgarn
2014-08-13 12:26 ` Brendan Hide
2014-08-12 16:38 ` Erkki Seppala
2014-08-12 11:00 ` Konstantinos Skarlatos
2014-08-13 11:01 ` David Pottage
2014-08-13 11:05 ` Konstantinos Skarlatos
2014-08-17 21:17 ` Chris Murphy
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=53E83035.8010603@gmail.com \
--to=ahferroin7@gmail.com \
--cc=arvimal@yahoo.in \
--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).