From: SandeepKsinha <sandeepksinha@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Simple inode question (ext2/3)
Date: Sat, 28 Mar 2009 00:57:44 -0700 (PDT) [thread overview]
Message-ID: <22754510.post@talk.nabble.com> (raw)
In-Reply-To: <20090225143821.GH7064@mit.edu>
Theodore Tso wrote:
>
> On Wed, Feb 25, 2009 at 10:59:22AM +0000, Felipe Franciosi wrote:
>> As a matter of fact, I didn't see any critics to the question below. I
>> can only assume that messing with inodes can look academic or not
>> depending on the phase of the moon or something.
>>
>> On 6 Jan 2009, at 10:36, Rohit Sharma wrote:
>>> I want to read data blocks from one inode
>>> and copy it to other inode.
>>>
>>> I mean to copy data from data blocks associated with one inode
>>> to the data blocks associated with other inode.
>>>
>>> Is that possible in kernel space.?
>>> --
>
>
>
> Actually, I asked Rohit what they were doing back September, 2008.
>
> http://article.gmane.org/gmane.comp.file-systems.ext4/9142
>
> Personally, I'm not really convinced by the approach which the fscops
> project is adopting, but that's up to them to figure out. I was
> amused though by their powerpoint slides which claim that they are "on
> the way to being accepted in the mainline kernel" --- that seems a
> little gradious, given that they haven't even submitted any code for
> review yet.
>
>
Hi Ted,
I know we became a bit futuristic at that point in time when we saw a mail
from Akira mentioning that you guys are planning to provide a ABI to provide
block allocation in restricted block group range(s), option(2) in the
following mail.
http://patchwork.ozlabs.org/patch/12877/
which would have made the OHSM work more simpler and compatible with
the current linux framework.
Also, there was a piece of code submitted from our end too, as a support to
the above option(2)
http://kerneltrap.org/mailarchive/linux-ext4/2009/1/26/4813934
asking if it would be feasible, if we go ahead and implement the same
for ext4.
Later, when we realised the complexities involved and saw some replies from
your end regarding the concept of OHSM. We have started being more cautious.
I believe we have also sent a recent reply to one of your mails on the
feedback to the idea of OHSM. It would be great if you can just pull out
some small amount of time to have a look at it atleast.
http://www.nabble.com/-RFC--PATCH-0-3--ext4%3A-online-defrag-(ver-1.0)-tc21742025.html
Thanks & Regards,
Rishi.
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
View this message in context: http://www.nabble.com/Simple-inode-question-%28ext2-3%29-tp22186566p22754510.html
Sent from the linux-ext4 mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-03-28 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 17:13 Simple inode question (ext2/3) Felipe Franciosi
2009-02-24 18:12 ` Felipe Franciosi
2009-02-24 19:07 ` Theodore Tso
2009-02-24 19:32 ` Felipe Franciosi
2009-02-24 21:05 ` Theodore Tso
2009-02-24 21:48 ` Felipe Franciosi
2009-02-25 4:06 ` Andreas Dilger
2009-02-25 10:59 ` Felipe Franciosi
2009-02-25 13:11 ` Theodore Tso
2009-02-25 14:10 ` Greg Freemyer
2009-02-25 14:38 ` Theodore Tso
2009-03-28 7:57 ` SandeepKsinha [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=22754510.post@talk.nabble.com \
--to=sandeepksinha@gmail.com \
--cc=linux-ext4@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).