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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- Regards, Sandeep. "To learn is to change. Education is a process that changes the learner." -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
