netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Yu <raise.sail@gmail.com>
To: Linux Netdev List <netdev@vger.kernel.org>
Subject: [PATCH 0/3] skbtrace v2: A trace infrastructure for networking subsystem
Date: Fri, 19 Oct 2012 14:16:04 +0800	[thread overview]
Message-ID: <5080F024.30608@gmail.com> (raw)

Hi,

  This patch set introduces to the tracing infrastructure for networking
subsystem, they are based on v3.6 source code.

  The changes from last version (v1):

  1. IPv4 mapped IPv6 sockets support, I found many applications use
     this mean to live on double stack environment.
  2. The BPF filter for connection based events, skbtrace constructs
     a temporarily sk_buff to run BPF program.
  3. Add three TCP trace events for RTTM, show active connection
     information, TCP internal timers. and show more states in
     tcp_ca_state event.
  4. Introduce to primary and secondary event support. That is secondary
     event only would be exported after its primary event is triggered.
     This could be used for reduce gathered trace points more, we can
     see this is another kind of trace point filter.
  5. Userland utility modularizaion.
  6. Code refactoring and bug fixes.

  I am going to add some sk_buff based events in next version (v3), so
we will could know such like how a sk_buff pass stack, how long it stay
in stack, how TSO/GSO/SACK/... split/merge them, and so on.

  You can get whole kernel source tree at github:

	https://github.com/Rover-Yu/skbtrace-userland
	https://github.com/Rover-Yu/skbtrace-kernel

  Welcome for suggestions.

  Thanks.

Yu

             reply	other threads:[~2012-10-19  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19  6:16 Li Yu [this message]
2012-10-19  7:33 ` [PATCH 0/3] skbtrace v2: A trace infrastructure for networking subsystem David Miller
2012-10-28 13:47   ` Li Yu

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=5080F024.30608@gmail.com \
    --to=raise.sail@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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).