Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752357AbaJFTqA (ORCPT ); Mon, 6 Oct 2014 15:46:00 -0400 Received: from resqmta-ch2-01v.sys.comcast.net ([69.252.207.33]:53906 "EHLO resqmta-ch2-01v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750909AbaJFTp6 (ORCPT ); Mon, 6 Oct 2014 15:45:58 -0400 Date: Mon, 6 Oct 2014 14:45:56 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: David Lang cc: Thomas Gleixner , Richard Cochran , linux-kernel@vger.kernel.org Subject: Re: Why do we still have 32 bit counters? Interrupt counters overflow within 50 days In-Reply-To: Message-ID: References: <20141003120345.GA6652@localhost.localdomain> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 6 Oct 2014, David Lang wrote: > No, tools recognize that things happen (wraps, reboots, etc) and have some > threshold that they say "if this value changes more than the threshold, > something happened and it's not valid to use this delta" > > This has been the case for decades. If you have a monitoring tool that does > not account for this sort of thing, you have an immature tool. Well maybe put those statement somewhere to find for those writing diagnostics tools that use the counters. -- 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/