From: Andi Kleen <andi@firstfloor.org>
To: Jovi Zhangwei <jovi.zhangwei@gmail.com>
Cc: Alexei Starovoitov <ast@plumgrid.com>,
Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Greg KH <gregkh@linuxfoundation.org>,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ktap and ebpf integration
Date: Sat, 5 Apr 2014 19:50:59 +0200 [thread overview]
Message-ID: <20140405175059.GT22728@two.firstfloor.org> (raw)
In-Reply-To: <CAGdX0WEbUszQv=xVK35aes=Qcw=D-0HztML0jBJsKy6hVCH8cA@mail.gmail.com>
> 4) var i = 0; trace *:* { i += 1}
> Assign global variable in here, there also can assign other
> value not 0, please show me how BPF do this.
> (See complex global usage example in samples/schedule/schedtimes.kp)
That's what I meant. BPF is essentially a statically typed
language. KTAP is dynamically typed. It's a very different
model.
Yes they are both Turing complete and likely could
be somehow translated into each other, but would
it be efficient and simple? No.
[essentially it's the "UNCOL problem" -- see
http://en.wikipedia.org/wiki/UNCOL
One size doesn't fit all in immediate languages]
-Andi
next prev parent reply other threads:[~2014-04-05 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 1:21 Jovi Zhangwei
2014-04-04 6:26 ` Alexei Starovoitov
2014-04-04 7:26 ` Jovi Zhangwei
2014-04-04 7:48 ` Ingo Molnar
2014-04-04 8:46 ` Jovi Zhangwei
2014-04-04 15:57 ` Alexei Starovoitov
2014-04-04 17:28 ` Alexei Starovoitov
2014-04-05 14:23 ` Jovi Zhangwei
2014-04-05 17:22 ` Alexei Starovoitov
2014-04-05 21:26 ` Jovi Zhangwei
2014-04-05 17:50 ` Andi Kleen [this message]
2014-04-04 14:20 ` Andi Kleen
2014-04-04 7:27 ` Ingo Molnar
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=20140405175059.GT22728@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ast@plumgrid.com \
--cc=gregkh@linuxfoundation.org \
--cc=jovi.zhangwei@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
Powered by JetHome