From: Luke Nelson <lukenels@cs.washington.edu>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: Song Liu <songliubraving@fb.com>,
Albert Ou <aou@eecs.berkeley.edu>, bpf <bpf@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Luke Nelson <luke.r.nels@gmail.com>,
Netdev <netdev@vger.kernel.org>,
Palmer Dabbelt <palmer@sifive.com>,
Alexei Starovoitov <ast@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Yonghong Song <yhs@fb.com>,
linux-riscv@lists.infradead.org, Martin KaFai Lau <kafai@fb.com>,
Xi Wang <xi.wang@gmail.com>
Subject: Re: [RFC PATCH bpf-next] RV32G eBPF JIT
Date: Wed, 26 Jun 2019 16:20:37 -0700 [thread overview]
Message-ID: <CADasFoC6ga_DuHL+RxLPzBhMHr+Jj5OgGkjuUgX0o6Rx5vsvdw@mail.gmail.com> (raw)
In-Reply-To: <CAJ+HfNgHOt4gMSq_gufwxb=cKekCfLrk-uGJuGeDiOeQV1-wwQ@mail.gmail.com>
On Mon, Jun 24, 2019 at 3:11 AM Björn Töpel <bjorn.topel@gmail.com> wrote:
> > - Far branches
> > These are not supported in RV64G either.
>
> This would be really nice to have, now that the size of BPF programs
> are getting larger.
I've sent out an updated version of the patch here, with support for
far branches: https://patchwork.ozlabs.org/patch/1123052
Thanks!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-27 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 22:59 [RFC PATCH bpf-next] RV32G eBPF JIT Luke Nelson
2019-06-24 10:11 ` Björn Töpel
2019-06-26 23:20 ` Luke Nelson [this message]
2019-06-24 16:45 ` Jiong Wang
2019-06-25 20:26 ` Luke Nelson
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=CADasFoC6ga_DuHL+RxLPzBhMHr+Jj5OgGkjuUgX0o6Rx5vsvdw@mail.gmail.com \
--to=lukenels@cs.washington.edu \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@sifive.com \
--cc=songliubraving@fb.com \
--cc=xi.wang@gmail.com \
--cc=yhs@fb.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).