From: adel.belkhiri@ensi-uma.tn (Adel Belkhiri)
Subject: [lttng-dev] Tracing network events in the kernel using lttng
Date: Thu, 11 Aug 2016 23:50:10 -0500 [thread overview]
Message-ID: <CAFMzwX6csrXt6aQwy0b7oW7CzfEKRr28uXYZcE4NhPrOWyCr4g@mail.gmail.com> (raw)
Hello,
I'm, from some time, working on tracing linux kernel using lttng to get
some information about the system' network activities. Tracing bare system
calls (--syscall) didn't give me much information so I realized that i
should first place some static probes in the kernel source files to be able
to trace (mainly) *TCP socket operations* (bind, accept, create, ...).
Running out of time in my project, I wonder if there are *any patch for the
kernel* that place those probes in the right source files.
My linux Kernel version is 3.2.0-4-486 and I'm using Lttng 2.7.
Thank very much you for your help.
Adel Belkhiri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160811/157f4f88/attachment.html>
next reply other threads:[~2016-08-12 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 4:50 Adel Belkhiri [this message]
2016-08-12 20:41 ` Mathieu Desnoyers
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=CAFMzwX6csrXt6aQwy0b7oW7CzfEKRr28uXYZcE4NhPrOWyCr4g@mail.gmail.com \
--to=adel.belkhiri@ensi-uma.tn \
/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