From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753218AbbF2QuL (ORCPT ); Mon, 29 Jun 2015 12:50:11 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:46808 "EHLO relay3-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752197AbbF2QuF (ORCPT ); Mon, 29 Jun 2015 12:50:05 -0400 Date: Mon, 29 Jun 2015 09:50:00 -0700 From: josh@joshtriplett.org To: Tejun Heo Cc: Geert Uytterhoeven , pmladek@suse.cz, Andrew Morton , "David S. Miller" , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , Kay Sievers , Linux Embedded Subject: Re: [PATCH 3/3] printk: implement support for extended console drivers Message-ID: <20150629165000.GA1483@cloud> References: <1430318704-32374-1-git-send-email-tj@kernel.org> <1430318704-32374-4-git-send-email-tj@kernel.org> <20150629152805.GM15805@mtj.duckdns.org> <20150629154914.GQ15805@mtj.duckdns.org> <20150629161355.GS15805@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150629161355.GS15805@mtj.duckdns.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 29, 2015 at 12:13:55PM -0400, Tejun Heo wrote: > On Mon, Jun 29, 2015 at 06:11:40PM +0200, Geert Uytterhoeven wrote: > > On Mon, Jun 29, 2015 at 5:49 PM, Tejun Heo wrote: > > > On Mon, Jun 29, 2015 at 05:47:49PM +0200, Geert Uytterhoeven wrote: > > >> > netconsole itself is optional & modular. I'm not sure making further > > >> > splits is called for, especially given the use cases. > > >> > > >> It could be a hidden option, selected by its users (e.g. netconsole). > > > > > > Hmmm... what do you mean? > > > > init/Kconfig: > > > > config PRINTK_EXT_LOG > > bool > > > > drivers/net/Kconfig: > > > > config NETCONSOLE > > tristate "Network console logging support" > > select PRINTK_EXT_LOG > > > > kernel/printk/printk.c: > > > > void console_unlock(void) > > { > > #ifdef CONFIG_PRINTK_EXT_LOG > > static char ext_text[CONSOLE_EXT_LOG_MAX]; > > #endif > > OIC, hmmm... yeah, I think doing it on-demand would be better but will > try to find out which way is better. Allocating the buffer dynamically is fine, but in that case the code to do so should ideally be compiled out. Since printk is used by almost *all* kernels, while netconsole is not, it's more critical to avoid allowing printk's size to balloon. - Josh Triplett