From: "Sandeep K Sinha" <sandeepksinha@gmail.com>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: "Rohit Sharma" <imreckless@gmail.com>,
ext4 <linux-ext4@vger.kernel.org>,
Kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: Copying Data Blocks
Date: Mon, 12 Jan 2009 12:18:01 +0530 [thread overview]
Message-ID: <37d33d830901112248r1616865aye537b5ff3f72780f@mail.gmail.com> (raw)
In-Reply-To: <804dabb00901110715x2baf84e8kc0fc5d6fa2512fe8@mail.gmail.com>
Hi Peter,
As our work veery tightly couples with the FS for our intial
implementation and we are working around with the inodes, we will
require to work at the filesystem level itself.
Though it may not be very feasible, but we will try to push everything
to the blockdev level once our base system is up and running.
Thanks a lot for your finding, I went through it and found that it
will be useful, but with some kind of tweaking around here and there.
We have taken note of the links that you have provided.
Thanks again.
On Sun, Jan 11, 2009 at 8:45 PM, Peter Teoh <htmldeveloper@gmail.com> wrote:
> Sorry.....some mistakes...a resent:
>
> Here are some tips on the blockdevice API:
>
> http://lkml.org/lkml/2006/1/24/287
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-01/msg09388.html
>
> as indicated, documentation is rather sparse in this area.
>
> not sure if anyone else have a summary list of blockdevice API and its
> explanation?
>
> not wrt the following "cleanup patch", i am not sure how the API will change:
>
> http://lwn.net/Articles/304485/
>
> thanks.
>
> On Tue, Jan 6, 2009 at 6:36 PM, Rohit Sharma <imreckless@gmail.com> 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.?
>> --
>
>
>
> --
> Regards,
> Peter Teoh
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
Regards,
Sandeep.
"To learn is to change. Education is a process that changes the learner."
prev parent reply other threads:[~2009-01-12 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 10:36 Copying Data Blocks Rohit Sharma
2009-01-06 11:21 ` kanishk rastogi
2009-01-06 13:24 ` Manish Katiyar
2009-01-06 14:12 ` rishi agrawal
2009-01-06 16:45 ` Rohit Sharma
2009-01-06 17:13 ` Manish Katiyar
2009-01-06 17:16 ` Rohit Sharma
2009-01-06 17:25 ` Rohit Sharma
2009-01-06 17:28 ` Manish Katiyar
2009-01-06 17:36 ` Rohit Sharma
2009-01-11 15:11 ` Peter Teoh
2009-01-11 15:15 ` Peter Teoh
2009-01-12 6:18 ` Rohit Sharma
2009-01-12 6:56 ` Sandeep K Sinha
2009-01-12 7:41 ` Peter Teoh
2009-01-12 8:26 ` Sandeep K Sinha
2009-01-12 6:48 ` Sandeep K Sinha [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=37d33d830901112248r1616865aye537b5ff3f72780f@mail.gmail.com \
--to=sandeepksinha@gmail.com \
--cc=htmldeveloper@gmail.com \
--cc=imreckless@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--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