From: Keith Owens <kaos@ocs.com.au>
To: Petko Manolov <pmanolov@lnxw.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: debugging eth driver
Date: Sun, 17 Mar 2002 12:36:43 +1100 [thread overview]
Message-ID: <25257.1016329003@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 16 Mar 2002 10:52:10 -0800." <3C93945A.8040305@lnxw.com>
On Sat, 16 Mar 2002 10:52:10 -0800,
Petko Manolov <pmanolov@lnxw.com> wrote:
>Alan Cox wrote:
>>>How am i supposed to get a feedback from the upper layers?
>>
>> Keep an eye on /proc/net/snmp
>
>It isn't very readable format.. Any other way or i have to
>read the code and see what the messages mean?
Quick and dirty script to neatly format /proc/net/snmp. BTW, there is
a mismatch in the ICMP list on 2.4.17, 26 headers and 27 values :(.
cat > /tmp/$$a <<\****
while(<>) {
chop;
(@f) = split;
if (++$line % 2) {
@head = @f;
}
else {
for ($i = 0; $i <= @f; ++$i) {
printf "%-25s%s\n", $head[$i], $f[$i];
}
}
}
****
cat /proc/net/snmp | perl /tmp/$$a
rm /tmp/$$a
next prev parent reply other threads:[~2002-03-17 1:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 22:36 RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-15 22:53 ` David S. Miller
2002-03-15 23:11 ` David Schwartz
2002-03-15 23:14 ` David S. Miller
2002-03-15 23:15 ` Alan Cox
2002-03-15 23:13 ` David Schwartz
2002-03-15 23:16 ` David S. Miller
2002-03-15 23:37 ` David S. Miller
2002-03-15 23:45 ` David S. Miller
2002-03-15 23:57 ` David S. Miller
2002-03-16 0:06 ` David Schwartz
2002-03-16 1:43 ` Alan Cox
2002-03-18 4:09 ` David S. Miller
2002-03-18 5:06 ` Mike Fedyk
2002-03-18 6:19 ` David S. Miller
2002-03-16 4:19 ` debugging eth driver Petko Manolov
2002-03-16 17:27 ` Alan Cox
2002-03-16 18:52 ` Petko Manolov
2002-03-16 20:56 ` Alan Cox
2002-03-17 1:36 ` Keith Owens [this message]
2002-03-17 3:37 ` Tomasz Kłoczko
2002-03-22 7:40 ` Cameron Simpson
2002-03-16 0:01 ` RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-16 0:12 ` Alan Cox
2002-03-15 23:59 ` Alan Cox
2002-03-15 23:53 ` David Schwartz
2002-03-15 23:54 ` David S. Miller
2002-03-16 0:14 ` Alan Cox
2002-03-15 23:40 ` Alan Cox
2002-03-17 10:00 ` bert hubert
2002-03-22 5:55 ` 2.5.7, IDE, 'handler not null', 'kernel timer added twice' David Schwartz
2002-03-22 6:10 ` Davide Libenzi
2002-03-22 10:59 ` Martin Dalecki
2002-03-22 20:13 ` Davide Libenzi
2002-03-23 13:12 ` Martin Dalecki
2002-03-22 6:31 ` Andre Hedrick
2002-03-15 23:19 ` RFC2385 (MD5 signature in TCP packets) support Alan Cox
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=25257.1016329003@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmanolov@lnxw.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
all inboxes | Powered by JetHome®