From: David Miller <davem@davemloft.net>
To: hpa@linux.intel.com
Cc: dborkman@redhat.com, ast@plumgrid.com, netdev@vger.kernel.org,
hagen@jauu.net, keescook@chromium.org, pmoore@redhat.com,
mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 8/9] net: filter: rework/optimize internal BPF interpreter's instruction set
Date: Tue, 25 Mar 2014 20:46:28 -0400 (EDT) [thread overview]
Message-ID: <20140325.204628.1622839093852736075.davem@davemloft.net> (raw)
In-Reply-To: <53321E3B.8080709@linux.intel.com>
From: "H. Peter Anvin" <hpa@linux.intel.com>
Date: Tue, 25 Mar 2014 17:24:27 -0700
> If you allow loops, it greatly increases the expressibility of the
> language, but we would really need another control to limit CPU usage.
We don't want super expressibility.
We want an extremely simple, trivial to validate, filtering language.
next prev parent reply other threads:[~2014-03-26 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1395749457-16178-1-git-send-email-dborkman@redhat.com>
2014-03-25 12:10 ` Daniel Borkmann
2014-03-26 0:17 ` David Miller
2014-03-26 0:24 ` H. Peter Anvin
2014-03-26 0:46 ` David Miller [this message]
2014-03-26 1:58 ` Alexei Starovoitov
2014-03-26 16:22 ` David Miller
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=20140325.204628.1622839093852736075.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=dborkman@redhat.com \
--cc=hagen@jauu.net \
--cc=hpa@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmoore@redhat.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
all inboxes | Powered by JetHome®