On Tue, 2015-05-26 at 13:40 +, David Laight wrote:
If the JIT compiler is only changing the encoding of the constants
in the x86 instructions (rather than changing the instructions themselves)
then there is likely to me an unmeasurable change in the execution time.
For instance I don't
From: Alexei Starovoitov
Sent: 22 May 2015 23:43
x86 has variable length encoding. x86 JIT compiler is trying
to pick the shortest encoding for given bpf instruction.
While doing so the jump targets are changing, so JIT is doing
multiple passes over the program. Typical program needs 3
From: Eric Dumazet
Sent: 26 May 2015 15:35
On Tue, 2015-05-26 at 13:40 +, David Laight wrote:
If the JIT compiler is only changing the encoding of the constants
in the x86 instructions (rather than changing the instructions themselves)
then there is likely to me an unmeasurable
On Tue, 2015-05-26 at 15:13 +, David Laight wrote:
Yes, interesting, a benchmark that manages to run a lot of code 'cold cache'.
We have binaries here at Google with 400 or 500 MBytes of text.
Not benchmark, super real workloads you know.
--
To unsubscribe from this list: send the line
From: Eric Dumazet
Sent: 26 May 2015 16:30
Yes, interesting, a benchmark that manages to run a lot of code 'cold
cache'.
We have binaries here at Google with 400 or 500 MBytes of text.
Not benchmark, super real workloads you know.
Indeed, and a lot of the code is likely to be
From: Alexei Starovoitov a...@plumgrid.com
Date: Fri, 22 May 2015 15:42:55 -0700
x86 has variable length encoding. x86 JIT compiler is trying
to pick the shortest encoding for given bpf instruction.
While doing so the jump targets are changing, so JIT is doing
multiple passes over the
On 05/23/2015 12:42 AM, Alexei Starovoitov wrote:
x86 has variable length encoding. x86 JIT compiler is trying
to pick the shortest encoding for given bpf instruction.
While doing so the jump targets are changing, so JIT is doing
multiple passes over the program. Typical program needs 3 passes.
