Re: 2.6.33 problems
From: Tejun Heo
Date: Tue Mar 02 2010 - 23:13:37 EST
On 03/03/2010 12:33 PM, werner@xxxxxxxxxxxxxxxxxxxxx wrote:
> dmesg isn't complete. That's a general problem. When we get 1 GB
> dmesg buffer in the kernel config ????
Kernel log can be incomplete for many reasons. In your case klogd
wasn't logging debug messages so I couldn't see pcpu debug info.
dmesg w/ sufficiently large -s combined with large kernel buffer
> Linux version 2.6.33-git7 (root@werner) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Tue Mar 2 06:15:19 GFT 2010
> setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:2 nr_node_ids:1
> PERCPU: Embedded 14 pages/cpu @c3c00000 s35876 r0 d21468 u2097152
> pcpu-alloc: s35876 r0 d21468 u2097152 alloc=1*4194304
> pcpu-alloc:  0 1
Here, the unit size is 2M and the chunk size 4M for the two possible
cpus. This isn't excessive at all and i386 shouldn't have much
problem accomodating it. Have you tried percpu_alloc=page?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/