Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758054Ab2FZBlK (ORCPT ); Mon, 25 Jun 2012 21:41:10 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:40333 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757862Ab2FZBlJ (ORCPT ); Mon, 25 Jun 2012 21:41:09 -0400 MIME-Version: 1.0 In-Reply-To: References: <1340651142.7037.2.camel@gandalf.stny.rr.com> <20120625150722.8cd4f45d.akpm@linux-foundation.org> <20120625235531.GB3652@kroah.com> <20120626002307.GA4389@kroah.com> From: Linus Torvalds Date: Mon, 25 Jun 2012 18:40:47 -0700 X-Google-Sender-Auth: KtPTwesEyrZ5kOjtDie1a3zZSik Message-ID: Subject: Re: [PATCH v3] printk: Have printk() never buffer its data To: Kay Sievers Cc: Greg Kroah-Hartman , Andrew Morton , Steven Rostedt , LKML , Ingo Molnar , Wu Fengguang , Joe Perches , "Paul E. McKenney" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 913 Lines: 24 On Mon, Jun 25, 2012 at 5:56 PM, Kay Sievers wrote: > > Buffering has nice effects though: > It makes continuation lines appear as one record in the buffer, not as > n individual prints with n headers. As I already mentioned, buffering for *logging* is different from buffering for *printing*. I think it might be a great idea to buffer for logging in order to generate one individual buffer record there. But it needs to be printed as it is generated. The printing and the recording really should be thought of as separate issues. You already record things that aren't printed, so they already aren't 1:1 relationships. Linus -- 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/