From: Daniel Borkmann <dborkman@redhat.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: netdev@vger.kernel.org, Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: [PATCH net-next] filter: add bpf_optimize_div()
Date: Thu, 20 Nov 2014 22:32:25 +0100 [thread overview]
Message-ID: <546E5DE9.3050602@redhat.com> (raw)
In-Reply-To: <1416512551-22252-1-git-send-email-kda@linux-powerpc.org>
On 11/20/2014 08:42 PM, Denis Kirjanov wrote:
> optimize_div() found in mips bpf jit is really usefull
> for other arches. So let's put it in filter.h
>
> CC: Alexei Starovoitov <ast@plumgrid.com>
> Signed-off-by: Denis Kirjanov <kda@linux-powerpc.org>
NAK
1) There's no user of this function (you name MIPS JIT, but
don't remove it from there) ...
2) It's not really specific or tied to the BPF API in particular,
so doesn't really belong here, rather some more generic kernel
header, iff anything.
> ---
> include/linux/filter.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/include/linux/filter.h b/include/linux/filter.h
> index ca95abd..b385637 100644
> --- a/include/linux/filter.h
> +++ b/include/linux/filter.h
> @@ -414,6 +414,17 @@ static inline void bpf_jit_dump(unsigned int flen, unsigned int proglen,
> print_hex_dump(KERN_ERR, "JIT code: ", DUMP_PREFIX_OFFSET,
> 16, 1, image, proglen, false);
> }
> +
> +static inline int bpf_optimize_div(u32 *k)
> +{
> + /* power of 2 divides can be implemented with right shift */
> + if (!(*k & (*k-1))) {
> + *k = ilog2(*k);
> + return 1;
> + }
> +
> + return 0;
> +}
> #else
> static inline void bpf_jit_compile(struct bpf_prog *fp)
> {
>
next prev parent reply other threads:[~2014-11-20 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 19:42 [PATCH net-next] filter: add bpf_optimize_div() Denis Kirjanov
2014-11-20 21:07 ` Alexei Starovoitov
2014-11-20 21:57 ` Daniel Borkmann
2014-11-21 9:22 ` Denis Kirjanov
2014-11-20 21:32 ` Daniel Borkmann [this message]
2014-11-21 5:46 ` Denis Kirjanov
2014-11-21 10:26 ` David Laight
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=546E5DE9.3050602@redhat.com \
--to=dborkman@redhat.com \
--cc=ast@plumgrid.com \
--cc=kda@linux-powerpc.org \
--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).