* [ltt-dev] Is Lttng able to work as a printk-like function？
@ 2010-05-26 15:32 jerome zh
2010-05-26 15:32 ` jerome zh
2010-05-26 15:32 ` jerome zh
0 siblings, 2 replies; 3+ messages in thread
From: jerome zh @ 2010-05-26 15:32 UTC (permalink / 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-0002.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ltt-dev] Is Lttng able to work as a printk-like function？
2010-05-26 15:32 [ltt-dev] Is Lttng able to work as a printk-like function？ jerome zh
2010-05-26 15:32 ` jerome zh
@ 2010-05-26 15:32 ` jerome zh
1 sibling, 0 replies; 3+ messages in thread
From: jerome zh @ 2010-05-26 15:32 UTC (permalink / 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/ltt-dev/attachments/20100526/bc67c9f0/attachment.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ltt-dev] Is Lttng able to work as a printk-like function？
2010-05-26 15:32 [ltt-dev] Is Lttng able to work as a printk-like function？ jerome zh
@ 2010-05-26 15:32 ` jerome zh
2010-05-26 15:32 ` jerome zh
1 sibling, 0 replies; 3+ messages in thread
From: jerome zh @ 2010-05-26 15:32 UTC (permalink / 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>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-26 15:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-05-26 15:32 [ltt-dev] Is Lttng able to work as a printk-like function？ jerome zh
2010-05-26 15:32 ` jerome zh
2010-05-26 15:32 ` jerome zh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox