search for: jnt

Hi all The machine provides the name service I got the following in the dmesg. What is it? Can I have rules to prevent it? UDP: bad checksum. From outside-ip:61479 to machine-ip:61 ulen 45 UDP: bad checksum. From outside-ip:62499 to machine-ip:61 ulen 45 UDP: bad checksum. From outside-ip:64135 to machine-ip:61 ulen 45 UDP: bad checksum. From outside-ip:64135 to machine-ip:61 ulen 45 UDP: bad

This is not a quite fair comparison. Other virtual machines must be doing garbage collection, while LLVM, as it is using C code, it is taking advantage of memory allocation by hand. On Fri, Jan 30, 2009 at 9:56 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > > The release of a new code generator in Mono 2.2 prompted me to benchmark the > performance of various VMs using the

Has anybody written an actuarial (life) survival procedure, this does not appear to be an option in the survival package? This approach is common in orthopaedic surgery to demonstrate the survival of prostheses. I need to apply the "modified" lower conf.int because of the censoring over time. I want a life table which I can then easily plot. Many thanks

The release of a new code generator in Mono 2.2 prompted me to benchmark the performance of various VMs using the SciMark2 benchmark on an 8x 2.1GHz 64-bit Opteron and I have published the results here: http://flyingfrogblog.blogspot.com/2009/01/mono-22.html The LLVM results were generated using llvm-gcc 4.2.1 on the C version of SciMark2 with the following command-line options: llvm-gcc