From: Ingo Molnar <mingo@kernel.org>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Daniel Borkmann <dborkman@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC net-next] tracing: accelerate tracing filters with BPF
Date: Wed, 14 May 2014 07:09:58 +0200 [thread overview]
Message-ID: <20140514050958.GB9448@gmail.com> (raw)
In-Reply-To: <CAMEtUuzct=k_9f4QTqRf2TG6mFCjpnfTjo+JkHYQDHKj_i2b+A@mail.gmail.com>
* Alexei Starovoitov <ast@plumgrid.com> wrote:
> On Tue, May 13, 2014 at 8:17 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Tue, 13 May 2014 19:55:11 -0700
> > Alexei Starovoitov <ast@plumgrid.com> wrote:
> >
> >> Tracing filters are parsing user supplied character string and constructing
> >> a predicate tree. filter_match_preds() was used to walk nodes of the tree to
> >> simulate matching of boolean expression.
> >>
> >
> > I applied this on top of net-next, from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> > (master branch)
> >
> > and got this compile error:
>
> Sorry I wasn't clear in the log.
> This patch depends on JIT patches that were posted separately.
> Since this one is RFC, I didn't want to mix them.
> JIT patches:
> http://patchwork.ozlabs.org/patch/348558/
> http://patchwork.ozlabs.org/patch/348559/
> http://patchwork.ozlabs.org/patch/348560/
Might make sense for you to get a korg account and stick such bits
into Git trees, to ease testing.
Thanks,
Ingo
next prev parent reply other threads:[~2014-05-14 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 2:55 [PATCH RFC net-next] tracing: accelerate tracing filters with BPF Alexei Starovoitov
2014-05-14 3:07 ` Steven Rostedt
2014-05-14 3:26 ` Alexei Starovoitov
2014-05-14 5:09 ` Ingo Molnar
2014-05-14 3:17 ` Steven Rostedt
2014-05-14 3:29 ` Alexei Starovoitov
2014-05-14 5:09 ` Ingo Molnar [this message]
2014-05-15 5:19 ` Alexei Starovoitov
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=20140514050958.GB9448@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.