From: Richard Cochran <richardcochran@gmail.com>
To: Ajith Adapa <adapa.ajith@gmail.com>
Cc: David Miller <davem@davemloft.net>,
raviraj.j1991@gmail.com, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: kenel level packet capturing
Date: Wed, 19 Oct 2011 14:30:25 +0200 [thread overview]
Message-ID: <20111019123025.GA9320@netboy.at.omicron.at> (raw)
In-Reply-To: <CADAe=++9WYg6nGH1vZ0BZKP5CDHO30i-pNVhBzgO9C-6FQX6cQ@mail.gmail.com>
On Wed, Oct 19, 2011 at 02:22:35PM +0530, Ajith Adapa wrote:
> Yeah you are right David. But ..
>
> For a newbie who just know more about linux userspace level need to
> know starting steps like where to start from and flow of packet might
> be confusing because of the level of abstraction being used. I guess
> it might take some time until you are really serious about making
> hands dirty :)
For working with or just reading kernel sources I recommend getting to
know the cscope tool. Do a "make cscope" and then use one of the front
end browsers.
If you use emacs, then you really should have this set
; When working on the kernel
(setq cscope-do-not-update-database t)
otherwise it tries to re-index after every search.
HTH,
Richard
next prev parent reply other threads:[~2011-10-19 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKj1SsP+GE=QqN8nx7aaAxXE8BODKb=vns_=SnbyySQjZp3-pg@mail.gmail.com>
2011-10-19 6:54 ` kenel level packet capturing 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 12:30 ` Richard Cochran [this message]
2011-10-19 12:37 ` Benjamin Poirier
2011-12-13 12:04 ` raviraj joshi
2011-12-13 18:36 ` David Miller
2011-12-14 10:46 ` raviraj joshi
2011-12-14 13:31 ` Jan Engelhardt
2011-12-14 16:09 ` David Miller
2011-12-15 15:19 ` Eduardo Panisset
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=20111019123025.GA9320@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=adapa.ajith@gmail.com \
--cc=davem@davemloft.net \
--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 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).