From: Jiong Wang <jiong.wang@netronome.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Jiong Wang <jiong.wang@netronome.com>,
daniel@iogearbox.net, bpf@vger.kernel.org,
netdev@vger.kernel.org, oss-drivers@netronome.com,
davem@davemloft.net, paul.burton@mips.com, udknight@gmail.com,
zlim.lnx@gmail.com, illusionist.neo@gmail.com,
naveen.n.rao@linux.ibm.com, sandipan@linux.ibm.com,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
jakub.kicinski@netronome.com
Subject: Re: [PATCH v9 bpf-next 00/17] bpf: eliminate zero extensions for sub-register writes
Date: Sat, 25 May 2019 10:09:13 +0100 [thread overview]
Message-ID: <87zhnagati.fsf@netronome.com> (raw)
In-Reply-To: <20190525020736.gty5sdcu5jakffet@ast-mbp.dhcp.thefacebook.com>
Alexei Starovoitov writes:
> On Fri, May 24, 2019 at 11:25:11PM +0100, Jiong Wang wrote:
>> v9:
>> - Split patch 5 in v8.
>> make bpf uapi header file sync a separate patch. (Alexei)
>
> 9th time's a charm? ;)
Yup :), it's all good things and helped us reaching a solution that fits
verifier's existing infra.
> Applied.
> Thanks a lot for all the hard work.
> It's a great milestone.
Thanks. And I guess the answer to the question:
"Q: BPF 32-bit subregister requirements"
inside Documentation/bpf/bpf_design_QA.rst now could be updated to
mention LLVM and JIT back-ends 32-bit supports, will send out an update on
this.
> Please follow up with an optimization for bpf_patch_insn_data()
> to make it scaleable and undo that workaround in scale tests.
Sure, will do.
Regards,
Jiong
prev parent reply other threads:[~2019-05-25 9:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 22:25 [PATCH v9 bpf-next 00/17] bpf: eliminate zero extensions for sub-register writes Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 01/17] bpf: verifier: mark verified-insn with sub-register zext flag Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 02/17] bpf: verifier: mark patched-insn " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 03/17] bpf: introduce new mov32 variant for doing explicit zero extension Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 04/17] bpf: verifier: insert zero extension according to analysis result Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 05/17] bpf: introduce new bpf prog load flags "BPF_F_TEST_RND_HI32" Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 06/17] tools: bpf: sync uapi header bpf.h Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 07/17] bpf: verifier: randomize high 32-bit when BPF_F_TEST_RND_HI32 is set Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 08/17] libbpf: add "prog_flags" to bpf_program/bpf_prog_load_attr/bpf_load_program_attr Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 09/17] selftests: bpf: adjust several test_verifier helpers for insn insertion Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 10/17] selftests: bpf: enable hi32 randomization for all tests Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 11/17] arm: bpf: eliminate zero extension code-gen Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 12/17] powerpc: " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 13/17] s390: " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 14/17] sparc: " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 15/17] x32: " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 16/17] riscv: " Jiong Wang
2019-05-24 22:25 ` [PATCH v9 bpf-next 17/17] nfp: " Jiong Wang
2019-05-25 2:07 ` [PATCH v9 bpf-next 00/17] bpf: eliminate zero extensions for sub-register writes Alexei Starovoitov
2019-05-25 9:09 ` Jiong Wang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhnagati.fsf@netronome.com \
--to=jiong.wang@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=illusionist.neo@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=paul.burton@mips.com \
--cc=sandipan@linux.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=udknight@gmail.com \
--cc=zlim.lnx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).