netdev - Re: [PATCH RFC bpf-next] bpf: per-register parent pointers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <551f7f45-e023-15ff-9064-71691363b9f0@solarflare.com>
Date:   Thu, 19 Jul 2018 17:54:01 +0100
From:   Edward Cree <ecree@...arflare.com>
To:     Alexei Starovoitov <ast@...nel.org>
CC:     <davem@...emloft.net>, <daniel@...earbox.net>,
        <netdev@...r.kernel.org>
Subject: Re: [PATCH RFC bpf-next] bpf: per-register parent pointers

On 18/07/18 04:54, Alexei Starovoitov wrote:
> I'd like to apply it, but I see the difference in insn_processed.
> Several cilium tests show favorable difference towards new liveness approach.
> selftests/bpf/test_xdp_noinline.o also shows the difference.
> I'm struggling to see why this patch would make such difference.
> Could you please help me analyze why such difference exists?
I'm also confused by it at present, but I am looking into it.
-Ed