On Thu, 2008-02-28 at 07:15 +, Jamie Lokier wrote:
Jerome Haltom wrote:
The problem is that during the rsync process the user's machine is
barely usable. The reason is because rsync reads these 2GB files... many
GBs of them. This causes the user's machine to repeatidly trash the page
On Thu, Feb 28, 2008 at 08:18:26AM -0500, Matt McCutchen wrote:
The distributed patch drop-cache.diff is an older version of this
patch. Wayne, would you care to update it?
His updated patch ignored all the improvments that I put into to the
first patch, and I didn't feel like redoing them.
On Thu, Feb 28, 2008 at 07:26:08AM -0800, Wayne Davison wrote:
If someone else would care to fix that, I'll certainly consider it.
Actually, now that I'm thinking about it, I recall that I didn't like
some things in how the patch worked, and began to work on signficant
changes, but never
Jerome Haltom wrote:
The problem is that during the rsync process the user's machine is
barely usable. The reason is because rsync reads these 2GB files... many
GBs of them. This causes the user's machine to repeatidly trash the page
cache. This really is Linux's fault. It should realize the
I would appreciate the addition of this option, which would cause files
opened by rsync to be opened using the O_DIRECT flag, on Linux, at
least. Let me explain my circumstance:
I use rsync to migration VMware disk images from one machine to another
while the VM is running. This works really
