From: David Miller <davem@davemloft.net>
To: shemminger@linux-foundation.org
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] display bound packet types
Date: Wed, 07 Mar 2007 18:56:40 -0800 (PST) [thread overview]
Message-ID: <20070307.185640.112291663.davem@davemloft.net> (raw)
In-Reply-To: <20070307164259.106c6c08@dxpl.pdx.osdl.net>
From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Wed, 7 Mar 2007 16:42:59 -0800
> While debugging I found it useful to see what packet types are in use.
>
> This creates /proc/net/ptype with the format:
>
> Type Device Function
> ALL eth0 [ffffffff880b01b6] :af_packet:packet_rcv_spkt+0x0
> 0800 [ffffffff802330f8] ip_rcv+0x0
> 0011 [ffffffff881021ef] :llc:llc_rcv+0x0
> 0004 [ffffffff881021ef] :llc:llc_rcv+0x0
> 0806 [ffffffff8043de7f] arp_rcv+0x0
> 86dd [ffffffff880c1b57] :ipv6:ipv6_rcv+0x0
>
> Is it worth the space?
I have no objections.
It would be nice to use kallsyms on that function address
though.
prev parent reply other threads:[~2007-03-08 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 0:42 [RFC] display bound packet types Stephen Hemminger
2007-03-08 2:56 ` David Miller [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=20070307.185640.112291663.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).