From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Andreas Rohner
<e0502196-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Contributing to NILFS
Date: Tue, 11 Dec 2012 10:46:28 +0400 [thread overview]
Message-ID: <1355208388.2627.16.camel@slavad-ubuntu> (raw)
In-Reply-To: <1355169902.803.19.camel@terok>
Hi Andreas,
On Mon, 2012-12-10 at 21:05 +0100, Andreas Rohner wrote:
> Hi,
>
> I am a computer science student from Austria and I am looking for a
> topic for my masters thesis. I am very interested in log-structured file
> systems and I thought of doing a few things from the TODO list on the
> website: http://www.nilfs.org/en/current_status.html
> I am particularly interested in the "Online defrag" feature, but I
> haven't looked into the source code yet. I have a few questions
> concerning that and any help would be greatly appreciated:
>
> 1. Has someone already started working on it?
As I know, you will be the first. :-)
> 2. Is there some fundamental difficulty that makes it hard to implement
> for a log-structured fs?
I think that the most fundamental possible issue can be a possible
performance degradation. But first of all, from my point of view, it
needs to discuss what the online defrag is and how it is possible to
implement it. What do you mean personally by online defrag? And how do
you imagine online defrag mechanism for NILFS2 in particular? When you
describe your understanding then it will be possible to discuss about
difficulties, I think. :-)
> 3. How much work would it entail? Is it doable for one well versed C
> programmer in 2 to 3 months?
>
I think that it is more easy to predict duration of some implementation
task when you know something about a developer. But, as I understand,
you don't familiar with NILFS2 source code. And how deep your experience
in Linux kernel implementation? So, it is not so easy to forecast
something. :-) I suggest to begin implementation. Anyway, it will be
very useful for your masters thesis, I think.
With the best regards,
Vyacheslav Dubeyko.
> best regards,
> Andreas Rohner
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-11 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 20:05 Contributing to NILFS Andreas Rohner
2012-12-11 6:46 ` Vyacheslav Dubeyko [this message]
2012-12-11 13:54 ` Andreas Rohner
2012-12-12 7:08 ` Vyacheslav Dubeyko
2012-12-12 15:30 ` Sven-Göran Bergh
[not found] ` <1355326242.67765.YahooMailNeo-mKBY30tKGRG2Y7dhQGSVAJOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2012-12-12 19:57 ` Vyacheslav Dubeyko
[not found] ` <706EE260-E8A2-410A-9211-FB4859516478-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-12-13 10:59 ` Sven-Göran Bergh
2012-12-16 17:45 ` Andreas Rohner
2012-12-17 6:30 ` Vyacheslav Dubeyko
2012-12-17 10:23 ` Andreas Rohner
2012-12-19 7:13 ` Vyacheslav Dubeyko
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=1355208388.2627.16.camel@slavad-ubuntu \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=e0502196-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).