Received:  by oss.sgi.com id <S42204AbQFVGnB>;
	Wed, 21 Jun 2000 23:43:01 -0700
Received: from dialup340.canberra.net.au ([203.33.188.212]:56585 "HELO halfway")
	by oss.sgi.com with SMTP id <S42190AbQFVGmp>;
	Wed, 21 Jun 2000 23:42:45 -0700
Received: from linuxcare.com.au (localhost [127.0.0.1])
	by halfway (Postfix) with ESMTP id 60DF68154
	for <netdev@oss.sgi.com>; Thu, 22 Jun 2000 16:42:39 +1000 (EST)
From:   Rusty Russell <rusty@linuxcare.com.au>
To:     netdev@oss.sgi.com
Subject: Re: RFC: Reporting dropped packets 
In-reply-to: Your message of "Thu, 22 Jun 2000 03:37:48 GMT."
             <39518A0C.59CFBFDC@uow.edu.au> 
Date:   Thu, 22 Jun 2000 16:42:39 +1000
Message-Id: <20000622064239.60DF68154@halfway>
Sender: owner-netdev@oss.sgi.com
Precedence: bulk
Return-Path: <owner-netdev@oss.sgi.com>
X-Orcpt: rfc822;netdev-outgoing

In message <39518A0C.59CFBFDC@uow.edu.au> Andrew Morton writes:
> Rusty Russell wrote:
> > 
> > There are a number of places in the network code where we drop packets
> > which people might be interested in knowing about (eg. my nat code,
> > CONFIG_IP_ROUTE_VERBOSE).
>
> Does this affect drivers?  Incoming packes dropped due to OOM,
> outgoing due to error recovery.

No, only systematic (`interesting') *IP* packet drops, not random
ones.  Trying to cover all packet drops was my original mistake, and
is fairly useless (turns out that `drop' is a vague definition: did we
`drop' a repeated TCP segment?).

I'm suggesting a trivial change here, not some giant packet
beancounter patch...

Rusty.
--
Hacking time.