From: Petru Paler <ppetru@ppetru.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-pre3+zerocopy: weird messages
Date: Mon, 15 Jan 2001 07:20:26 +0200 [thread overview]
Message-ID: <20010115072026.A918@ppetru.net> (raw)
In-Reply-To: <20010114121105.B1394@ppetru.net> <14945.32886.671619.99921@pizda.ninka.net> <20010114124549.D1394@ppetru.net> <14945.34414.185794.396720@pizda.ninka.net> <20010114132845.F1394@ppetru.net> <14945.36440.59585.376942@pizda.ninka.net> <20010114141003.G1394@ppetru.net> <20010114151257.J1394@ppetru.net> <14945.42973.905573.579075@pizda.ninka.net>
In-Reply-To: <14945.42973.905573.579075@pizda.ninka.net>; from davem@redhat.com on Sun, Jan 14, 2001 at 05:21:33AM -0800
On Sun, Jan 14, 2001 at 05:21:33AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > Got more "udp v4 hw csum failure" messages but still no "UDP packet
> > with bad csum was fragmented".
>
> OK, last experiment :-) Add this patch, and watch to see if
> the UDP "InErrors" field in /proc/net/snmp has a non-zero value after
> letting it run for a while. Thanks.
Ok, here it is:
grey:/proc/net# uptime
12:14am up 11:01, 1 user, load average: 0.45, 0.47, 0.41
grey:/proc/net# cat snmp
Ip: Forwarding DefaultTTL InReceives InHdrErrors InAddrErrors ForwDatagrams InUnknownProtos InDiscards InDelivers OutRequests OutDiscards OutNoRoutes ReasmTimeout ReasmReqds ReasmOKs ReasmFails FragOKs FragFails FragCreates
Ip: 2 64 8340770 0 0 0 0 8 8290517 1359445 6 0 0 0 0 0 0 0 0
Icmp: InMsgs InErrors InDestUnreachs InTimeExcds InParmProbs InSrcQuenchs InRedirects InEchos InEchoReps InTimestamps InTimestampReps InAddrMasks InAddrMaskReps OutMsgs OutErrors OutDestUnreachs OutTimeExcds OutParmProbs OutSrcQuenchs OutRedirects OutEchos OutEchoReps OutTimestamps OutTimestampReps OutAddrMasks OutAddrMaskReps
Icmp: 7370 446 3846 772 0 39 0 2708 0 0 0 0 0 9661 0 6953 0 0 0 0 0 2708 0 0 0 0
Tcp: RtoAlgorithm RtoMin RtoMax MaxConn ActiveOpens PassiveOpens AttemptFails EstabResets CurrEstab InSegs OutSegs RetransSegs InErrs OutRsts
Tcp: 0 0 0 0 16025 0 128 0 20 825925 921717 44521 189 28300
Udp: InDatagrams NoPorts InErrors OutDatagrams
Udp: 7500511 6953 30 428614
--
Petru Paler, mailto:ppetru@ppetru.net
http://www.ppetru.net - ICQ: 41817235
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-15 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-14 10:11 2.4.0-pre3+zerocopy: weird messages Petru Paler
2001-01-14 10:33 ` David S. Miller
2001-01-14 10:45 ` Petru Paler
2001-01-14 10:58 ` David S. Miller
2001-01-14 11:28 ` Petru Paler
2001-01-14 11:32 ` David S. Miller
2001-01-14 12:10 ` Petru Paler
2001-01-14 13:12 ` Petru Paler
2001-01-14 13:21 ` David S. Miller
2001-01-14 18:08 ` Petru Paler
2001-01-15 5:20 ` Petru Paler [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=20010115072026.A918@ppetru.net \
--to=ppetru@ppetru.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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.