linux-kernel - Re: [RFC PATCH v7 00/37] perf tools: filtering events using eBPF programs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <557FB286.8040302@huawei.com>
Date:	Tue, 16 Jun 2015 13:22:14 +0800
From:	"Wangnan (F)" <wangnan0@...wei.com>
To:	Alexei Starovoitov <ast@...mgrid.com>, <acme@...nel.org>,
	<brendan.d.gregg@...il.com>, <daniel@...earbox.net>,
	<namhyung@...nel.org>, <masami.hiramatsu.pt@...achi.com>,
	<paulus@...ba.org>, <a.p.zijlstra@...llo.nl>, <mingo@...hat.com>,
	<jolsa@...nel.org>, <dsahern@...il.com>
CC:	<linux-kernel@...r.kernel.org>, <lizefan@...wei.com>,
	<hekuang@...wei.com>, <xiakaixu@...wei.com>, <pi3orama@....com>
Subject: Re: [RFC PATCH v7 00/37] perf tools: filtering events using eBPF
 programs



On 2015/6/13 0:58, Alexei Starovoitov wrote:
>
> btw, what compile times do you see?
> On my machine compiling basic hello_world.c with #include bpf_helpers.h
> and few kernel headers take: 0.02 sec
> So using .c is quite instant. Feels like interpreted language ;)

Sorry I didn't see your question for several days.

It takes 1.63 seconds for perf to compile lock_page.c I posted in 
previous mail.
Most of the time is consumed by kernel include directories detection. If 
skip the
detector and passes options through cmdline, time reduced to 0.2 seconds. My
environment is a server equipped with Intel Xeon 2.4G cores. However the 
storage
is NFS based.

Thank you.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/