mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move LOG_BUF_SIZE to header file
Date: Tue, 17 Dec 2002 09:41:51 +0000	[thread overview]
Message-ID: <20021217094150.A2467@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0212121517300.19827-100000@dragon.pdx.osdl.net>; from rddunlap@osdl.org on Mon, Dec 16, 2002 at 10:11:42PM -0800

On Mon, Dec 16, 2002 at 10:11:42PM -0800, Randy.Dunlap wrote:
> --- ./arch/i386/Kconfig%LOGBUF	Sun Dec 15 18:07:47 2002
> +++ ./arch/i386/Kconfig	Sun Dec 15 20:45:09 2002
> @@ -1573,6 +1573,43 @@
>  	  If you don't debug the kernel, you can say N, but we may not be able
>  	  to solve problems without frame pointers.
> 
> +choice
> +	prompt "Kernel log buffer size"
> +	default LOG_BUF_128KB if ARCH_S390
> +	default LOG_BUF_64KB if X86_NUMAQ || IA64
> +	default LOG_BUF_32KB if SMP
> +	default LOG_BUF_16KB

yuck.  Why don't you just add and integer LOG_BUG_SHIFT symbol that can
be freely choosen?


  parent reply	other threads:[~2002-12-17  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 19:16 Randy.Dunlap
2002-12-10 19:41 ` Andrew Morton
2002-12-17  6:11   ` [PATCH] " Randy.Dunlap
2002-12-17  6:39     ` James H. Cloos Jr.
2002-12-17 17:22       ` Randy.Dunlap
2002-12-17  9:41     ` Christoph Hellwig [this message]
2002-12-17 17:14       ` Randy.Dunlap
2002-12-17 17:27     ` Andrew Morton
2002-12-17 22:33       ` [PATCH] (v3) move LOG_BUF_SIZE to header/config Randy.Dunlap
2002-12-18  1:14         ` Andrew Morton
2002-12-18  4:03           ` Randy.Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021217094150.A2467@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome