From: dborkman@redhat.com (Daniel Borkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/3] ARM: net: bpf_jit: make code generation less dependent on struct sk_filter.
Date: Sat, 27 Apr 2013 00:30:19 +0200 [thread overview]
Message-ID: <517AFFFB.9090201@redhat.com> (raw)
In-Reply-To: <CAKU6vyYOZ-24TSyLa8t6Oipib37fE1gtvM8nWj2TDzVw-tv0jA@mail.gmail.com>
On 04/27/2013 12:18 AM, Xi Wang wrote:
> Thanks for CCing. One way to clean up this would be to refactor the
> bpf jit interface as:
>
> bpf_func_t bpf_jit_compile(struct sock_filter *filter, unsigned int flen);
> void bpf_jit_free(bpf_func_t bpf_func);
>
> Then both packet and seccomp filters can share the unified interface.
> Also, we don't need seccomp_filter_get_len() and other helpers.
>
> Do you want me to rebase my patch against linux-next and see how that goes?
Sure, whatever works for you. Not sure if it will still make it though.
Also, as Eric already mentioned earlier, please do not top-post your mails!
I think one reminder should be sufficient for that. ;-)
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: Xi Wang <xi.wang@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Nicolas Schichan <nschichan@freebox.fr>,
Will Drewry <wad@chromium.org>,
Mircea Gherzan <mgherzan@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel.borkmann@tik.ee.ethz.ch>,
netdev@vger.kernel.org
Subject: Re: [PATCH V3 2/3] ARM: net: bpf_jit: make code generation less dependent on struct sk_filter.
Date: Sat, 27 Apr 2013 00:30:19 +0200 [thread overview]
Message-ID: <517AFFFB.9090201@redhat.com> (raw)
In-Reply-To: <CAKU6vyYOZ-24TSyLa8t6Oipib37fE1gtvM8nWj2TDzVw-tv0jA@mail.gmail.com>
On 04/27/2013 12:18 AM, Xi Wang wrote:
> Thanks for CCing. One way to clean up this would be to refactor the
> bpf jit interface as:
>
> bpf_func_t bpf_jit_compile(struct sock_filter *filter, unsigned int flen);
> void bpf_jit_free(bpf_func_t bpf_func);
>
> Then both packet and seccomp filters can share the unified interface.
> Also, we don't need seccomp_filter_get_len() and other helpers.
>
> Do you want me to rebase my patch against linux-next and see how that goes?
Sure, whatever works for you. Not sure if it will still make it though.
Also, as Eric already mentioned earlier, please do not top-post your mails!
I think one reminder should be sufficient for that. ;-)
next prev parent reply other threads:[~2013-04-26 22:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 17:27 [PATCH V3] Support for JIT in Seccomp BPF filters Nicolas Schichan
2013-04-24 17:27 ` Nicolas Schichan
2013-04-24 17:27 ` [PATCH V3 1/3] seccomp: add generic code for jitted seccomp filters Nicolas Schichan
2013-04-24 17:27 ` Nicolas Schichan
2013-04-24 17:27 ` [PATCH V3 2/3] ARM: net: bpf_jit: make code generation less dependent on struct sk_filter Nicolas Schichan
2013-04-24 17:27 ` Nicolas Schichan
2013-04-24 17:41 ` Daniel Borkmann
2013-04-24 17:41 ` Daniel Borkmann
2013-04-26 14:04 ` Arnd Bergmann
2013-04-26 14:04 ` Arnd Bergmann
2013-04-26 19:26 ` Andrew Morton
2013-04-26 19:26 ` Andrew Morton
2013-04-26 19:47 ` Daniel Borkmann
2013-04-26 19:47 ` Daniel Borkmann
2013-04-26 20:09 ` Andrew Morton
2013-04-26 20:09 ` Andrew Morton
2013-04-26 22:01 ` Daniel Borkmann
2013-04-26 22:01 ` Daniel Borkmann
2013-04-26 22:18 ` Xi Wang
2013-04-26 22:18 ` Xi Wang
2013-04-26 22:30 ` Daniel Borkmann [this message]
2013-04-26 22:30 ` Daniel Borkmann
2013-04-26 23:33 ` David Miller
2013-04-26 23:33 ` David Miller
2013-04-26 23:33 ` David Miller
2013-04-24 17:27 ` [PATCH V3 3/3] ARM: net: bpf_jit: add support for jitted seccomp filters Nicolas Schichan
2013-04-24 17:27 ` Nicolas Schichan
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=517AFFFB.9090201@redhat.com \
--to=dborkman@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 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.