From: jeromezhr@gmail.com (jerome zh)
Subject: [ltt-dev] Is Lttng able to work as a printk-like function？
Date: Wed, 26 May 2010 23:32:03 +0800 [thread overview]
Message-ID: <AANLkTilskdsZ3vIpoY6AreI_7dnqXGzSCQFcyVs67gf0@mail.gmail.com> (raw)
Message-ID: <20100526153203.73AadgwKU8HuF9s3WcLxklGihsSUiuYwoLgZrScSwLY@z> (raw)
Hi all,
In our projects, we used to call printk() in the ip stack to show some ip
header information each time a packet comes in.
But when the packet comes too frequently, the system becomes overload
because of too many printk().
So we are wondering if we can do this by lttng, since its performance is
quite high?
If lttng cannot directly print them to the screen, recording ip header
information to the trace files is also a good choice.
BTW, I've read the marker.txt and tracepoint.txt. But these examples don't
cover such subject.
Any suggestions? Thanks in advance.
--
Regards,
Jerome
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100526/bc67c9f0/attachment-0001.htm>
next reply other threads:[~2010-05-26 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:32 jerome zh [this message]
2010-05-26 15:32 ` jerome zh
2010-05-26 15:32 ` jerome zh
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=AANLkTilskdsZ3vIpoY6AreI_7dnqXGzSCQFcyVs67gf0@mail.gmail.com \
--to=jeromezhr@gmail.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