public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "rishi agrawal" <postrishi@gmail.com>
To: "Manish Katiyar" <mkatiyar@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: Tue, 6 Jan 2009 19:42:34 +0530	[thread overview]
Message-ID: <5feb302e0901060612p4e114953pb6e297778aa7c0a4@mail.gmail.com> (raw)
In-Reply-To: <ea11fea30901060524n559a48f1h85bbf27be5b30b50@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

yes i suppose the donor inode is known
moreover the receiver inode's number is also known

On Tue, Jan 6, 2009 at 6:54 PM, Manish Katiyar <mkatiyar@gmail.com> wrote:

> On Tue, Jan 6, 2009 at 4:06 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.
>
> Copying 4K chunk of data itself is a costly operation. and depending
> on the size of your donor inode this can be huge . Why do you want to
> do that ? Do you know the inode of the donor inode ?
>
> thanks -
> Manish
> >
> > Is that possible in kernel space.?
> > --
> > 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
> >
> --
> 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
>



-- 
Regards,
Rishi B. Agrawal

[-- Attachment #2: Type: text/html, Size: 1957 bytes --]

  reply	other threads:[~2009-01-06 14:12 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 [this message]
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

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=5feb302e0901060612p4e114953pb6e297778aa7c0a4@mail.gmail.com \
    --to=postrishi@gmail.com \
    --cc=imreckless@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mkatiyar@gmail.com \
    /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