Re: [PATCH] Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Robert Read
On Tue, Feb 20, 2001 at 02:53:04PM -0600, Thomas Dodd wrote: > Robert Read wrote: > > Why not just make the config option in Kbytes. > and do: > > #define LOG_BUF_LEN (CONFIG_PRINTK_BUF_LEN * 1024) > This is good idea, but I believe LOG_BUF_LEN needs to be a power of 2. A bitmask is used in s

Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Ishikawa
Robert Read wrote: > I have used 128k and larger buffer sizes, and I just noticed this > fragment in the RedHat Tux Webserver patch. It creates a 2MB buffer: > > I am encouraged to try a large buffer then. Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

Re: [PATCH] Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Thomas Dodd
Thomas Dodd wrote: > > Robert Read wrote: > > > > Ok, here is a simple patch to add a config option, I'm compiling it > > now, so it's not tested yet. One question: what is the best way to > > force this option to be a power of 2? > > Why not just make the config option in Kbytes. > and do: >

Re: [PATCH] Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Thomas Dodd
Robert Read wrote: > > On Tue, Feb 20, 2001 at 01:37:16PM -0600, Thomas Dodd wrote: > > Robert Read wrote: > > > > > > On Wed, Feb 21, 2001 at 02:30:08AM +0900, Ishikawa wrote: > > > > > > > > Has anyone tried 128K buffer size in kernel/printk.c > > > > and still have the kernel boot (without > >

[PATCH] Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Robert Read
On Tue, Feb 20, 2001 at 01:37:16PM -0600, Thomas Dodd wrote: > Robert Read wrote: > > > > On Wed, Feb 21, 2001 at 02:30:08AM +0900, Ishikawa wrote: > > > > > > Has anyone tried 128K buffer size in kernel/printk.c > > > and still have the kernel boot (without > > > hard to notice memory corruption

Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Thomas Dodd
Robert Read wrote: > > On Wed, Feb 21, 2001 at 02:30:08AM +0900, Ishikawa wrote: > > > > Has anyone tried 128K buffer size in kernel/printk.c > > and still have the kernel boot (without > > hard to notice memory corruption problems and other subtle bugs)? > > Any hints and tips will be appreciat

Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Robert Read
On Wed, Feb 21, 2001 at 02:30:08AM +0900, Ishikawa wrote: > > Has anyone tried 128K buffer size in kernel/printk.c > and still have the kernel boot (without > hard to notice memory corruption problems and other subtle bugs)? > Any hints and tips will be appreciated. I have used 128k and larger

kernel/printk.c: increasing the buffer size to capture devfsd debug messages.

2001-02-20 Thread Ishikawa
Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Subject: kernel/printk.c: increase the buffer size to capture devfsd debug messages. Short Question: Can I use (128*1024) for the buffer size in kernel/printk.c and still boot the kernel using loadlin? Lo