search for: reusuing

Hi. I have more questions regarding llvm and using it as a jit for our purposes. Also, let me confess that I haven't actually used llvm yet (I'm still prototyping using gnu's libjit). Some of the issues that have come up from that work so far leads to me these questions: 1) We intend to use llvm as a jit in our expression compiler at compile-time only. At runtime, the x86 code

...and an external host. Two hosts were connected through 40gb mlx4 cards. With both busy_poll and busy_read are set to 50 in guest, 1 byte netperf tcp_rr shows 127% improvement: transaction rate was increased from 8353.33 to 18966.87. Changes from V2: - Avoid introducing new states and spinlocks by reusuing the NAPI state - Fix the budget calculation in virtnet_poll() - Drop patch 1/3 from V2 since it was useless Changes from V1: - split the patch info smaller ones - add more details about test setup/configuration Jason Wang (2): virtio-net: introduce virtnet_receive() virtio-net: rx busy poll...

...and an external host. Two hosts were connected through 40gb mlx4 cards. With both busy_poll and busy_read are set to 50 in guest, 1 byte netperf tcp_rr shows 127% improvement: transaction rate was increased from 8353.33 to 18966.87. Changes from V2: - Avoid introducing new states and spinlocks by reusuing the NAPI state - Fix the budget calculation in virtnet_poll() - Drop patch 1/3 from V2 since it was useless Changes from V1: - split the patch info smaller ones - add more details about test setup/configuration Jason Wang (2): virtio-net: introduce virtnet_receive() virtio-net: rx busy poll...

On Tue, Mar 23, 2010 at 4:44 PM, Shasank Chavan <shanko_chavano at hotmail.com> wrote: > Hi.  I have more questions regarding llvm and using it as a jit for our > purposes.  Also, let me confess that I haven't actually used llvm yet (I'm > still prototyping using gnu's libjit).  Some of the issues that have come up > from that work so far leads to me these questions:

Hi Reid. Thanks for your response. We will be running this code in different processes across different nodes. Basically we have thousands of "executor" processes that are solely responsible for executing this code generated at compile-time across partitioned data. Rather than each one of these processes invoking the jit and compiling with full opts and all of that, we believe it may

If you really trying to avoid linking everything into a shared library (easiest choice), consider splitting up the compilation into a few more steps: 1) Compile and optimize once as part of your build, target LLVM bitcode instead of machine code 2) Ship .bc files out to each node 3) Fix-up call instructions in a BasicBlockPass, run JIT without any/many additional IR optimizations enabled This

If you distribute the .bc to a new machine and JIT it there, you wouldn't need to apply any relocations to call instructions, since the JIT will get all the offsets right when it does code generation on the node. I would strongly recommend the shared library approach over this one, because JIT compile time is dominated by code generation, not optimization. If you distribute the .bcs, then