From: Daniel Borkmann <daniel@iogearbox.net>
To: Jiong Wang <jiong.wang@netronome.com>
Cc: xdp-newbies@vger.kernel.org, llvm-dev@lists.llvm.org,
iovisor-dev@lists.iovisor.org, oss-drivers@netronome.com,
ys114321@gmail.com
Subject: Re: [PATCH RFC 0/4] Initial 32-bit eBPF encoding support
Date: Wed, 20 Sep 2017 01:24:09 +0200 [thread overview]
Message-ID: <59C1A719.90909@iogearbox.net> (raw)
In-Reply-To: <f7eb81db-a758-d49d-4c09-08a017b02e98@netronome.com>
On 09/20/2017 01:20 AM, Jiong Wang wrote:
> On 18/09/2017 22:29, Daniel Borkmann wrote:
[...]
>> Great to see work in this direction! Can we also enable to use / emit
>> all the 32bit BPF_ALU instructions whenever possible for the currently
>> available bpf targets while at it (which only use BPF_ALU64 right now)?
>
> Hi Daniel,
>
> Thanks for the feedback.
>
> I think we could also enable the use of all the 32bit BPF_ALU under currently
> available bpf targets. As we now have 32bit register set support, we could make
> i32 type as legal type to prevent it be promoted into i64, then hook it up with i32
> ALU patterns, will look into this.
Great, thanks!
next prev parent reply other threads:[~2017-09-19 23:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 20:47 [PATCH RFC 0/4] Initial 32-bit eBPF encoding support Jiong Wang
2017-09-18 20:47 ` [PATCH RFC 1/4] Improve instruction encoding descriptions Jiong Wang
2017-09-18 20:47 ` [PATCH RFC 2/4] Improve class inheritance in instruction patterns Jiong Wang
2017-09-18 20:47 ` [PATCH RFC 3/4] New 32-bit register set Jiong Wang
2017-09-19 6:44 ` [iovisor-dev] " Y Song
2017-09-19 23:10 ` Jiong Wang
2017-09-22 4:55 ` Y Song
2017-09-18 20:47 ` [PATCH RFC 4/4] Initial 32-bit ALU encoding support in assembler Jiong Wang
2017-09-18 21:29 ` [PATCH RFC 0/4] Initial 32-bit eBPF encoding support Daniel Borkmann
2017-09-19 23:20 ` Jiong Wang
2017-09-19 23:24 ` Daniel Borkmann [this message]
2017-09-21 18:56 ` [iovisor-dev] " Alexei Starovoitov
2017-09-21 19:36 ` Daniel Borkmann
2017-09-22 16:24 ` [oss-drivers] " Jakub Kicinski
2017-09-23 5:03 ` Yonghong Song
2017-09-23 8:41 ` Jakub Kicinski
2017-09-23 14:42 ` Y Song
2017-09-24 5:46 ` Alexei Starovoitov
2017-09-19 4:49 ` Fulvio Risso
2017-09-19 22:56 ` Jiong Wang
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=59C1A719.90909@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=iovisor-dev@lists.iovisor.org \
--cc=jiong.wang@netronome.com \
--cc=llvm-dev@lists.llvm.org \
--cc=oss-drivers@netronome.com \
--cc=xdp-newbies@vger.kernel.org \
--cc=ys114321@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.