From: Sandipan Das <sandipan@linux.ibm.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: naveen.n.rao@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: powerpc64: optimize JIT passes for bpf function calls
Date: Mon, 3 Dec 2018 18:56:00 +0530 [thread overview]
Message-ID: <03a23ff9-1337-74dc-74e5-c5132909f8be@linux.ibm.com> (raw)
In-Reply-To: <0e55ce74-ea93-06cf-cc67-28708f978bc2@iogearbox.net>
Hi Daniel,
On 03/12/18 6:18 PM, Daniel Borkmann wrote:
>
> Thanks for the patch, just to clarify, it's targeted at bpf-next and
> not bpf, correct?
>
This patch is targeted at the bpf tree.
This depends on commit e2c95a61656d ("bpf, ppc64: generalize fetching
subprog into bpf_jit_get_func_addr") which is already available in the
bpf tree.
Thanks,
Sandipan
next prev parent reply other threads:[~2018-12-03 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:21 [PATCH bpf] bpf: powerpc64: optimize JIT passes for bpf function calls Sandipan Das
2018-12-03 12:48 ` Daniel Borkmann
2018-12-03 13:26 ` Sandipan Das [this message]
2018-12-03 22:53 ` Daniel Borkmann
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=03a23ff9-1337-74dc-74e5-c5132909f8be@linux.ibm.com \
--to=sandipan@linux.ibm.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=netdev@vger.kernel.org \
/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).