similar to: Improve --inplace updates on pathological inputs

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to

Ubuntu-10.04, x86, stock. I''m running into a situation where a server goes pathological. Basically, it becomes excruciatingly slow. I can get things through the file system, but a simple file touch can take 6 - 12 hours. Top shows various btrfs processes hard at work - typically 100% of a cpu, (four cpu server), and the machine shows a load of just over 4. Some flush-btrfs, some

On Sun, Nov 1, 2009 at 6:02 AM, Peter Dalgaard <p.dalgaard at biostat.ku.dk> w= rote: > macrakis at alum.mit.edu wrote: >> >> nchar(with(list(2),ls())) gives an internal error. This is of course >> a peculiar call (no names in the list), but the error is not caught >> cleanly. >> >> It is not clear from the documentation whether with(list(2)...) is

https://bugzilla.samba.org/show_bug.cgi?id=8666 Summary: --debug=all9 fail Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au QAContact: rsync-qa at

Folks, I wonder if anything could be said about the distribution of a random variate x, where x = N(0,1)/N(0,1) Obviously x is pathological because it could be 0/0. If we exclude this point, so the set is {x/(0/0)}, does x have a well defined distribution? or does it exist a distribution that approximates x. (The case could be generalized of course to N(mu1, sigma1)/N(mu2, sigma2) and one

nchar(with(list(2),ls())) gives an internal error. This is of course a peculiar call (no names in the list), but the error is not caught cleanly. It is not clear from the documentation whether with(list(2)...) is allowable; if it is not, it should presumably give an error. If it is, then ls shouldn't have problems with the resulting environment. > qq <- with(list(2),ls())

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

Hello all, Thanks for all the ideas. I liked the remote to remote idea and have told my guide about it. Anyways, can anybody tell me which files to look into, if I want to look at the code for file reconstruction. I have studied Dr. Tridgell's thesis on the Rsync Algorithm and have understood the working of the algorithm. Now, I am trying to read the code to understand it better. Any help

On 11/30/2012 6:36 PM, Lang Hames wrote: > > > RBP is used as the frame pointer on x86 (hence its automatic > appearance in your code), and shouldn't be allocated to any vreg in > function bar. Loading/saving RBP should be managed by the stack frame > setup/teardown code. > If it doesn't already, your allocator should filter out reserved > registers (See

Hi, When using rsync-3.0.2 through 3.0.5, I get this error on a large dataset syncing from machine-a to machine-b: $ /bin/rsync -aHSz /local/. machine-b:/local/. invalid len passed to map_ptr: -1737287498 rsync error: error in file IO (code 11) at fileio.c(188) [sender=3.0.5] This happens no matter which side initiates the connection, so this fails in the same way: $ /bin/rsync -aHSz

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

https://bugzilla.samba.org/show_bug.cgi?id=7778 Summary: --inplace does extra WRITE operations Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: ildar at altlinux.ru

Author: perrin Repository: /hg/zfs-crypto/gate Revision: a593e64c4739242e2eb3a43ea296996000af0c2d Log message: 6413731 pathologically slower fsync on 32 bit systems Files: update: usr/src/uts/common/fs/zfs/sys/zil.h update: usr/src/uts/common/fs/zfs/zil.c

Appdb entry (http://appdb.winehq.org/objectManager.php?sClass=application&iId=8352) I'm trying to get all my games to run under linux, but of cause a few are giving me problems, and Pathologic is one of the few that really bothers me. As far as I can tell, the game uses DirectX9, Windows Media format (cinematics), and OpenAL. Of the three, the WMF dependency is the most annoying, as it

I''ve been seeing read and write performance pathologies with Linux ext3 over iSCSI to zvols, especially with small writes. Does running a journalled filesystem to a zvol turn the block storage into swiss cheese? I am considering serving ext3 journals (and possibly swap too) off a raw, hardware-mirrored device. Before I do (and I''ll write up any results) I''d like to know

Maybe security related mails should be sent elsewhere? I didn't notice any so here it goes: sender.c:receive_sums() s->count = read_int(f); .. s->sums = (struct sum_buf *)malloc(sizeof(s->sums[0])*s->count); if (!s->sums) out_of_memory("receive_sums"); for (i=0; i < (int) s->count;i++) { s->sums[i].sum1 = read_int(f);

https://bugzilla.samba.org/show_bug.cgi?id=10518 Summary: rsync hangs (100% cpu) Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: syzop at vulnscan.org QAContact: