From: Keith Owens <kaos@ocs.com.au>
To: Matt Mackall <mpm@selenic.com>
Cc: Jeff Moyer <jmoyer@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] teach netconsole how to do syslog 
In-reply-to: Your message of "Fri, 25 Jun 2004 14:11:01 EST."
             <20040625191101.GD25826@waste.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 26 Jun 2004 12:26:46 +1000
Message-ID: <25929.1088216806@ocs3.ocs.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 988
Lines: 21

On Fri, 25 Jun 2004 14:11:01 -0500, 
Matt Mackall <mpm@selenic.com> wrote:
>Yep, we get one UDP packet per printk currently, which works for most
>things, but not everything. This could be changed to a buffered
>approach, but that breaks one of my favorite debugging techniques -
>adding an alphabet soup of single-character printks to trace tricky
>call paths. 
>
>So we could add a __printk that doesn't flush to outputs for stuff
>like the above, or just live with it.

Other way round.  Keep printk as is and use a buffered approach for
printk over netconsole.  netconsole gets complete lines which is what
you want 99.9% of the time.  Add __printk or printk_unbuffered for the
.1% of debugging output that really wants unbuffered output.

-
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/