From: Daniel Borkmann <dborkman@redhat.com>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: Chema Gonzalez <chema@google.com>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH] filter: added BPF random opcode
Date: Wed, 16 Apr 2014 10:32:40 +0200 [thread overview]
Message-ID: <534E4028.6090501@redhat.com> (raw)
In-Reply-To: <CAMEtUuw3-LEuwJ2cAQ+F-tu_-wzy4HK4ZteAuJpYfY9hW66+FA@mail.gmail.com>
On 04/16/2014 08:24 AM, Alexei Starovoitov wrote:
...
> At the same time I think the extension technic itself is nice and clean :)
> The call approach is definitely how we envisioned it to be used.
> Right now we have only x86-64 jit that is waiting for net-next to be opened,
> but this extension will be automatically jit-ed due to 'call approach'. Nice.
Ok, in terms of JIT it's definitely better that way, agreed.
next prev parent reply other threads:[~2014-04-16 8:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 18:16 [PATCH] filter: added BPF random opcode Chema Gonzalez
2014-04-16 6:24 ` Alexei Starovoitov
2014-04-16 8:32 ` Daniel Borkmann [this message]
2014-04-17 0:19 ` Chema Gonzalez
2014-04-17 1:38 ` Eric Dumazet
2014-04-18 20:21 ` Alexei Starovoitov
2014-04-21 16:21 ` [PATCH v2] " Chema Gonzalez
2014-04-21 21:46 ` Alexei Starovoitov
2014-04-21 21:54 ` Chema Gonzalez
2014-04-21 22:20 ` Alexei Starovoitov
2014-04-21 23:19 ` Chema Gonzalez
2014-04-22 2:42 ` Alexei Starovoitov
2014-04-22 21:10 ` Daniel Borkmann
2014-04-23 1:29 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-04-14 23:02 [PATCH] " Chema Gonzalez
2014-04-15 7:24 ` Daniel Borkmann
2014-04-15 14:41 ` Eric Dumazet
2014-04-15 15:04 ` Daniel Borkmann
2014-04-15 16:22 ` Chema Gonzalez
2014-04-15 16:30 ` Chema Gonzalez
2014-04-15 16:44 ` Daniel Borkmann
2014-04-15 18:19 ` Chema Gonzalez
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=534E4028.6090501@redhat.com \
--to=dborkman@redhat.com \
--cc=ast@plumgrid.com \
--cc=chema@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).