All of lore.kernel.org
 help / color / mirror / Atom feed
From: aruna.hewapathirane@gmail.com (Aruna Hewapathirane)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to browse the code
Date: Wed, 12 Apr 2017 22:23:44 -0400	[thread overview]
Message-ID: <CAFSeFg8vTQ-MT1jn9MmrVDPSXhh7ooiCWxAkM0s_PQ4bma6CZg@mail.gmail.com> (raw)
In-Reply-To: <CABGNecxcLj4tpF5pC-wU=SWNj5CzVrfwxJToz9h8TyCjwfyntQ@mail.gmail.com>

> On Tue, Apr 11, 2017 at 3:17 PM, Code Soldier1 <codesoldier1@gmail.com>
wrote:
> Folks,

> Can you tell me how to effectively browse linux kernel code. I am
> familiar with lxr etc but they do not do what I want or atleast I do
> not know how to.

> I am looking for something that can list all the places that a certain
> field of a certain structure is used. For example, sk_buff has a field
> called destructor, but so do many other data structures. How do I
> search for places where just the destructor field of sk_buff.

> Thanks a lot.

Ask yourself *how* is the destructor invoked ? You can find *how* here: SKB
socket accounting <http://vger.kernel.org/%7Edavem/skb_sk.html>

So now if you run:
find . -name '*.c' | xargs grep -r -F "skb->destructor"

you will have what you are looking for :)

Hope this helps and this will help: http://vger.kernel.org/~davem/skb.html

<http://vger.kernel.org/%7Edavem/skb_sk.html>
Aruna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170412/b27e9de9/attachment.html 

      parent reply	other threads:[~2017-04-13  2:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 19:17 How to browse the code Code Soldier1
2017-04-11 20:13 ` Mandeep Sandhu
2017-04-11 23:56   ` manty kuma
     [not found]     ` <CABGNecz-3SU=yfPQEJKM_uLd3-7Opn01S30ymOidpGF3cJY23Q@mail.gmail.com>
2017-04-13 10:39       ` manty kuma
2017-04-13 11:41         ` Daniel.
2017-04-13 11:50           ` Quentin Lambert
2017-04-13 14:22           ` valdis.kletnieks at vt.edu
     [not found]   ` <CABGNeczyadNCKYjLwWoK8N3o9dJdseUrAYCwFPx16DFr2Je7ng@mail.gmail.com>
2017-04-12 21:28     ` Mandeep Sandhu
     [not found]       ` <CABGNecxf3RnZH-kJ2VbC5JPuj=0Ka-1GPBA2x5R_tYyHLLm5EQ@mail.gmail.com>
     [not found]         ` <CAC+QLdTbDM9kTxE96ErcrHNMCoEhNbV1LKU+xcWaxj+j_DP1aA@mail.gmail.com>
2017-04-12 21:47           ` Mandeep Sandhu
2017-04-13  2:23 ` Aruna Hewapathirane [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=CAFSeFg8vTQ-MT1jn9MmrVDPSXhh7ooiCWxAkM0s_PQ4bma6CZg@mail.gmail.com \
    --to=aruna.hewapathirane@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.