From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: raviraj joshi <raviraj.j1991@gmail.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
netfilter@vger.kernel.org
Subject: Re: kenel level packet capturing
Date: Wed, 19 Oct 2011 08:37:33 -0400 [thread overview]
Message-ID: <20111019123733.GA21324@synalogic.ca> (raw)
In-Reply-To: <CAKj1SsOnYsOXjRBKm+=hTnEiesXrC3h0Q-KN2b61nPSQud9wMA@mail.gmail.com>
On 11/10/19 12:24, raviraj joshi wrote:
> Hi,
>
> We are making a kernel level packet capture module as a part of our BE project .
> We are finding it difficult to understand kenel networking code.
> We studied structures and functions like sk_buff, netif_rx(),dev_alloc_skb.
>
> However we were not able to trace the actual path a simple packet follows.
You might find
http://vger.kernel.org/netconf2011_slides/jesse_brandeburg_netconf2011.pdf
interesting. It contains call chains of UDP processing at all levels in
the stack (driver, below ip stack, above ip stack) for tx and rx.
-Ben
next prev parent reply other threads:[~2011-10-19 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 15:19 kenel level packet capturing raviraj joshi
2011-10-18 20:41 ` Bruno Prémont
2011-10-19 6:54 ` raviraj joshi
2011-10-19 7:12 ` Eric Dumazet
2011-10-19 7:13 ` David Miller
2011-10-19 8:52 ` Ajith Adapa
2011-10-19 8:52 ` Ajith Adapa
2011-10-19 12:30 ` Richard Cochran
2011-10-19 12:37 ` Benjamin Poirier [this message]
2011-12-13 12:04 ` raviraj joshi
2011-12-13 18:36 ` David Miller
2011-12-14 9:34 ` Jasper Spaans
2011-12-14 9:56 ` Eric Dumazet
2011-12-14 10:46 ` raviraj joshi
2011-12-14 13:31 ` Jan Engelhardt
2011-12-14 13:31 ` Jan Engelhardt
2011-12-14 16:09 ` David Miller
2011-12-15 15:19 ` Eduardo Panisset
-- strict thread matches above, loose matches on Subject: below --
2011-12-14 14:55 chetan loke
2011-12-14 15:04 ` Jasper Spaans
2011-12-14 15:07 ` Eric Dumazet
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=20111019123733.GA21324@synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=raviraj.j1991@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.