From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: hagen@jauu.net, rui314@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: filter: Convert the BPF VM to threaded code
Date: Tue, 09 Aug 2011 07:00:27 +0200 [thread overview]
Message-ID: <1312866027.2531.42.camel@edumazet-laptop> (raw)
In-Reply-To: <20110801.175705.2074393848482150971.davem@davemloft.net>
Le lundi 01 août 2011 à 17:57 -0700, David Miller a écrit :
> Maybe it won't if we use an enum and make sure all enum values are handled
> in the switch? :-)
I tried this idea since its already an enum and all enum values are
handled in the witch, but all gcc versions I used still generate the
useless compare and branch (always predicted by modern CPU, so harmless
anyway ?)
348: 83 c3 08 add $0x8,%ebx
34b: 66 83 3b 37 cmpw $0x37,(%ebx)
34f: 77 f7 ja 348 <sk_run_filter+0x18>
351: 0f b7 03 movzwl (%ebx),%eax
354: ff 24 85 34 01 00 00 jmp *0x134(,%eax,4)
It would be nice to try the jump table idea and avoid the array
indirection and get instead :
add $0xc,%ebx
jmp *(ebx)
(But this would need to use a larger kernel_sock_filter with not an u16
code, but the target address).
diff --git a/include/linux/filter.h b/include/linux/filter.h
index 741956f..f2a1b37 100644
--- a/include/linux/filter.h
+++ b/include/linux/filter.h
@@ -171,7 +171,7 @@ static inline void bpf_jit_free(struct sk_filter *fp)
#define SK_RUN_FILTER(FILTER, SKB) sk_run_filter(SKB, FILTER->insns)
#endif
-enum {
+enum bpf_inst {
BPF_S_RET_K = 1,
BPF_S_RET_A,
BPF_S_ALU_ADD_K,
diff --git a/net/core/filter.c b/net/core/filter.c
index 36f975f..ea1f467 100644
--- a/net/core/filter.c
+++ b/net/core/filter.c
@@ -119,17 +119,15 @@ unsigned int sk_run_filter(const struct sk_buff *skb,
u32 tmp;
int k;
+ fentry--;
/*
* Process array of filter instructions.
*/
- for (;; fentry++) {
-#if defined(CONFIG_X86_32)
+ for (;;) {
#define K (fentry->k)
-#else
- const u32 K = fentry->k;
-#endif
- switch (fentry->code) {
+ fentry++;
+ switch ((enum bpf_inst)fentry->code) {
case BPF_S_ALU_ADD_X:
A += X;
continue;
@@ -350,11 +348,6 @@ load_b:
A = 0;
continue;
}
- default:
- WARN_RATELIMIT(1, "Unknown code:%u jt:%u tf:%u k:%u\n",
- fentry->code, fentry->jt,
- fentry->jf, fentry->k);
- return 0;
}
}
next prev parent reply other threads:[~2011-08-09 5:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 8:10 [PATCH] net: filter: Convert the BPF VM to threaded code Rui Ueyama
2011-07-29 9:30 ` Eric Dumazet
2011-07-30 5:09 ` Rui Ueyama
2011-07-30 6:04 ` Eric Dumazet
2011-07-30 6:20 ` Eric Dumazet
2011-07-30 9:55 ` Francois Romieu
2011-08-01 18:16 ` Hagen Paul Pfeifer
2011-08-01 18:37 ` Eric Dumazet
2011-08-02 0:57 ` David Miller
2011-08-09 5:00 ` Eric Dumazet [this message]
2011-08-09 8:29 ` Hagen Paul Pfeifer
2011-08-09 8:36 ` Eric Dumazet
2011-08-09 8:53 ` Hagen Paul Pfeifer
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=1312866027.2531.42.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=rui314@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