From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752255AbaFZXUS (ORCPT ); Thu, 26 Jun 2014 19:20:18 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:33708 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751986AbaFZXUQ (ORCPT ); Thu, 26 Jun 2014 19:20:16 -0400 Date: Thu, 26 Jun 2014 16:20:14 -0700 From: Andrew Morton To: "Luis R. Rodriguez" Cc: "Luis R. Rodriguez" , gregkh@linuxfoundation.org, hpa@linux.intel.com, linux-kernel@vger.kernel.org, Andrew Lunn , Stephen Warren , Michal Hocko , Petr Mladek , Joe Perches , Arun KS , Kees Cook , Davidlohr Bueso , Chris Metcalf Subject: Re: [PATCH v8 4/4] printk: allow increasing the ring buffer depending on the number of CPUs Message-Id: <20140626162014.156f6741c7d9d3234879054f@linux-foundation.org> In-Reply-To: <20140626231630.GI27687@wotan.suse.de> References: <1403124337-14886-1-git-send-email-mcgrof@do-not-panic.com> <1403124337-14886-4-git-send-email-mcgrof@do-not-panic.com> <20140623154134.43ac7ab63896cd9ebcba84b6@linux-foundation.org> <20140624002050.GC27687@wotan.suse.de> <20140623174533.88663e64.akpm@linux-foundation.org> <20140624010554.GF27687@wotan.suse.de> <20140626144117.3412feee6234786be098259d@linux-foundation.org> <20140626231630.GI27687@wotan.suse.de> X-Mailer: Sylpheed 3.2.0beta5 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Jun 2014 01:16:30 +0200 "Luis R. Rodriguez" wrote: > > > Another note -- since this option depends on SMP and !BASE_SMALL technically > > > num_possible_cpus() won't ever return something smaller than or equal to 1 > > > but because of the default values chosen the -1 on the compuation does affect > > > whether or not this will trigger on > 64 CPUs or >= 64 CPUs, keeping the > > > -1 means we require > 64 CPUs. > > > > hm, that sounds like more complexity. > > > > > This all can be changed however we like but the language and explained logic > > > would just need to be changed. > > > > Let's start out simple. What's wrong with doing > > > > log buf len = max(__LOG_BUF_LEN, nr_possible_cpus * per-cpu log buf len) > > Sure, you already took in the patch series though so how would you like to > handle a respin, you just drop the last patch and we respin it? A fresh patch would suit. That's if you think it is a reasonable approach - you've thought about this stuff more than I have!