Date: Mon, 28 Nov 2005 23:02:24 -0800 (PST)
Message-Id: <20051128.230224.36483799.davem@davemloft.net>
To: kjak@users.sourceforge.net, kjak@ispwest.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] Resetting packet statistics
From: "David S. Miller" <davem@davemloft.net>
In-Reply-To: <d0d8bf3880744a79a8a5c26c8459e9ac.kjak@ispwest.com>
References: <d0d8bf3880744a79a8a5c26c8459e9ac.kjak@ispwest.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 971
Lines: 26

From: "Kris Katterjohn" <kjak@ispwest.com>
Date: Mon, 28 Nov 2005 22:28:18 -0800

> From: David S. Miller
> Sent: 11/28/2005 10:12:38 PM
> > You can't change existing behavior in order to get the new behavior
> > you want.  Some applications might be depending upon what happens
> > currently.
> 
> Is there a way to work around this?

Why not create a new call that doesn't reset the statistic,
and change your application to invoke it instead of the call
which exists?

That's one backwards compatible way to fix things like this.

Or, you can create a new call that says "from now on, do not
reset statistics on calls using this socket."  That's another
clean, and backwards compatible way, to deal with this
kind of issue.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/