From: David Miller <davem@davemloft.net>
To: xiakaixu@huawei.com
Cc: daniel@iogearbox.net, ast@plumgrid.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
wangnan0@huawei.com, pi3orama@163.com
Subject: Re: [PATCH net-next] bpf: fix build warnings and add function read_trace_pipe()
Date: Wed, 12 Aug 2015 16:39:26 -0700 (PDT) [thread overview]
Message-ID: <20150812.163926.1443596955889419582.davem@davemloft.net> (raw)
In-Reply-To: <1439372273-69958-1-git-send-email-xiakaixu@huawei.com>
From: Kaixu Xia <xiakaixu@huawei.com>
Date: Wed, 12 Aug 2015 09:37:53 +0000
> There are two improvements in this patch:
> 1. Fix the build warnings;
> 2. Add function read_trace_pipe() to print the result on
> the screen;
>
> Before this patch, we can get the result through /sys/kernel/de
> bug/tracing/trace_pipe and get nothing on the screen.
> By applying this patch, the result can be printed on the screen.
> $ ./tracex6
> ...
> tracex6-705 [003] d..1 131.428593: : CPU-3 19981414
> sshd-683 [000] d..1 131.428727: : CPU-0 221682321
> sshd-683 [000] d..1 131.428821: : CPU-0 221808766
> sshd-683 [000] d..1 131.428950: : CPU-0 221982984
> sshd-683 [000] d..1 131.429045: : CPU-0 222111851
> tracex6-705 [003] d..1 131.429168: : CPU-3 20757551
> sshd-683 [000] d..1 131.429170: : CPU-0 222281240
> sshd-683 [000] d..1 131.429261: : CPU-0 222403340
> sshd-683 [000] d..1 131.429378: : CPU-0 222561024
> ...
>
> Signed-off-by: Kaixu Xia <xiakaixu@huawei.com>
Applied, thanks.
prev parent reply other threads:[~2015-08-12 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:37 [PATCH net-next] bpf: fix build warnings and add function read_trace_pipe() Kaixu Xia
2015-08-12 16:25 ` Alexei Starovoitov
2015-08-12 23:39 ` David Miller [this message]
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=20150812.163926.1443596955889419582.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
--cc=xiakaixu@huawei.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;
as well as URLs for NNTP newsgroup(s).