From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Tracing network events in the kernel using lttng
Date: Fri, 12 Aug 2016 20:41:45 +0000 (UTC) [thread overview]
Message-ID: <1729632151.9416.1471034505021.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAFMzwX6csrXt6aQwy0b7oW7CzfEKRr28uXYZcE4NhPrOWyCr4g@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2245 bytes --]
----- On Aug 12, 2016, at 12:50 AM, Adel Belkhiri <adel.belkhiri at ensi-uma.tn> wrote:
> 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.
You'll be interested in recent commits that made their way into lttng
master branch:
At the networking level:
commit e5990fd415d46da69523dfe7943bc3168664fde8
Author: Geneviève Bastien <gbastien+lttng at versatic.net>
Date: Mon Jul 11 09:34:02 2016 -0400
net: Add IPv4/IPv6 header data to net_* tracepoints
commit 9cf9736a1715a1fec4857fac2784a12596675ce2
Author: Geneviève Bastien <gbastien+lttng at versatic.net>
Date: Tue Jul 12 13:26:14 2016 -0400
net: Add TCP header data to net_* tracepoints
and for the accept and connect syscalls (in stable-2.8 and
master):
commit 7ca580f8aca4f8c2b9e0066ad52ebfc226b3d645
Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date: Thu Jul 24 12:47:46 2014 -0400
Extract input/output arguments from accept and connect syscalls
This is all you should need to extract the kind of information you
want. Perhaps we should add other specialized system call
tracepoint probe functions to get more information about the
arguments, but it should not require any kernel modification nor
dynamic probing.
Hoping this helps!
Mathieu
> Thank very much you for your help.
> Adel Belkhiri
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160812/6ee5dce2/attachment.html>
prev parent reply other threads:[~2016-08-12 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 4:50 Adel Belkhiri
2016-08-12 20:41 ` Mathieu Desnoyers [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=1729632151.9416.1471034505021.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.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