From: Paul Eggert <eggert@CS.UCLA.EDU>
To: "jeff.liu" <jeff.liu@oracle.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
Jim Meyering <jim@meyering.net>,
bug-coreutils@gnu.org, Joel Becker <Joel.Becker@oracle.com>,
Chris Mason <chris.mason@oracle.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Tao Ma <tao.ma@oracle.com>
Subject: Re: bug#6131: [PATCH]: fiemap support for efficient sparse file copy
Date: Tue, 15 Jun 2010 14:09:22 -0700 [thread overview]
Message-ID: <4C17EC02.7040505@cs.ucla.edu> (raw)
In-Reply-To: <4C11F451.8040304@oracle.com>
On 06/11/2010 01:31 AM, jeff.liu wrote:
> + fiemap->fm_flags = FIEMAP_FLAG_SYNC;
If I'm reading the Linux source code correctly,
this forces all the dirty blocks in the input file to disk, and
forces the kernel to wait until all those blocks actually hit the disk.
We don't need that; there shouldn't be a need to force any
blocks to hit the disk. All that 'cp' needs to know is: please tell me
the next block which might contain nonzero data. Is there some way
that we can get that information without forcing the input file's
blocks to disk?
next prev parent reply other threads:[~2010-06-15 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BE41FFF.4020809@oracle.com>
[not found] ` <871vdho68j.fsf@meyering.net>
[not found] ` <4BEC0BCC.3080906@oracle.com>
[not found] ` <87k4qyl6lw.fsf@meyering.net>
[not found] ` <4BF683CC.3060407@oracle.com>
[not found] ` <4BF6ABE7.3020600@oracle.com>
[not found] ` <877hmpeivx.fsf@meyering.net>
[not found] ` <4BFF763A.9010205@oracle.com>
[not found] ` <8763286kni.fsf@meyering.net>
[not found] ` <4C0275FA.1030901@oracle.com>
[not found] ` <874ohpywri.fsf@meyering.net>
[not found] ` <87y6exuc5i.fsf@meyering.net>
[not found] ` <874ohdu5b8.fsf@meyering.net>
[not found] ` <87eighs1t9.fsf@meyering.net>
[not found] ` <4C0FA93C.6020205@oracle.com>
[not found] ` <87iq5sp7eg.fsf@meyering.net>
[not found] ` <4C108CB9.8010805@oracle.com>
[not found] ` <4C11798B.6090500@cs.ucla.edu>
2010-06-11 0:31 ` bug#6131: [PATCH]: fiemap support for efficient sparse file copy Sunil Mushran
2010-06-11 8:31 ` jeff.liu
2010-06-11 12:38 ` Jim Meyering
2010-06-11 14:03 ` Eric Sandeen
2010-06-13 3:37 ` jeff.liu
2010-06-15 21:09 ` Paul Eggert [this message]
2010-06-15 21:11 ` Paul Eggert
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=4C17EC02.7040505@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Joel.Becker@oracle.com \
--cc=bug-coreutils@gnu.org \
--cc=chris.mason@oracle.com \
--cc=jeff.liu@oracle.com \
--cc=jim@meyering.net \
--cc=linux-ext4@vger.kernel.org \
--cc=sunil.mushran@oracle.com \
--cc=tao.ma@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.