Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261939AbVANKij (ORCPT ); Fri, 14 Jan 2005 05:38:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261941AbVANKij (ORCPT ); Fri, 14 Jan 2005 05:38:39 -0500 Received: from colin2.muc.de ([193.149.48.15]:3845 "HELO colin2.muc.de") by vger.kernel.org with SMTP id S261939AbVANKii (ORCPT ); Fri, 14 Jan 2005 05:38:38 -0500 Date: 14 Jan 2005 11:38:36 +0100 Date: Fri, 14 Jan 2005 11:38:36 +0100 From: Andi Kleen To: Nikita Danilov Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.11-rc1-mm1 Message-ID: <20050114103836.GA71397@muc.de> References: <20050114002352.5a038710.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 22 On Fri, Jan 14, 2005 at 01:27:27PM +0300, Nikita Danilov wrote: > Andi Kleen writes: > > [...] > > > > > Preferably that would be only the fastest options (extremly simple > > per CPU buffer with inlined fast path that drop data on buffer overflow), > > Logging mechanism that loses data is worse than useless. It's only too > often that one spends a lot of time trying to reproduce some condition > with logging on, only to find out that nothing was logged. When you have a timing bug and your logger starts to block randomly you also won't debug anything. Fix is to make your buffers bigger. -Andi - 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/