From: Eric Dumazet <eric.dumazet@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [PATCH v2] net: filter: Just In Time compiler
Date: Thu, 14 Apr 2011 18:05:47 +0200 [thread overview]
Message-ID: <1302797147.3248.32.camel@edumazet-laptop> (raw)
In-Reply-To: <4DA71876.803@redhat.com>
Le jeudi 14 avril 2011 à 18:53 +0300, Avi Kivity a écrit :
> IMO, it will. I'll try to have gcc optimize your example filter later.
Sure you can JIT a C program from bpf. It should take maybe 30 minutes.
It certainly is more easy than JIT an binary/assembly code :)
Now take a look how I call slowpath, I am not sure gcc will actually
generate better code because of C conventions.
Loading a filter should be fast.
Invoking a compiler is just too much work for BPF.
Remember loading a filter is available to any user.
This idea would be good for netfilter stuff, because we dont load
iptables rules that often.
But still, the netfilter mainloop can be converted as a kernel JIT, most
probably. All the complex stuff (matches, targets) must call external
procedures anyway.
next prev parent reply other threads:[~2011-04-14 16:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 22:28 [PATCH v1] net: filter: Just In Time compiler Eric Dumazet
2011-04-02 22:50 ` Hagen Paul Pfeifer
2011-04-03 5:41 ` Eric Dumazet
2011-04-02 22:53 ` Ben Hutchings
2011-04-03 13:56 ` [PATCH v2] " Eric Dumazet
2011-04-04 5:07 ` David Miller
2011-04-04 5:21 ` Eric Dumazet
2011-04-14 14:40 ` Avi Kivity
2011-04-14 14:55 ` Hagen Paul Pfeifer
2011-04-14 15:41 ` Avi Kivity
2011-04-14 15:45 ` Eric Dumazet
2011-04-14 15:53 ` Avi Kivity
2011-04-14 16:05 ` Eric Dumazet [this message]
2011-04-20 7:41 ` Avi Kivity
2011-04-20 8:07 ` Eric Dumazet
2011-04-20 8:14 ` David Miller
2011-04-20 8:27 ` Hagen Paul Pfeifer
2011-04-20 19:27 ` Eric Dumazet
2011-04-28 6:05 ` David Miller
2011-04-20 8:12 ` David Miller
2011-04-14 15:40 ` Eric Dumazet
2011-04-14 15:45 ` Avi Kivity
2011-04-03 5:43 ` [PATCH v1] " David Miller
2011-04-03 9:04 ` Eric Dumazet
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=1302797147.3248.32.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=hagen@jauu.net \
--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