Re: [PATCH] Add debugging aid for memory initialisation problems

[mel@skynet.ie (Mel Gorman)]

On (27/11/06 16:08), Andi Kleen didst pronounce:
> 
> > > So how many new lines does that add overall?
> > 
> > I don't know for sure, but it's probably around the 150 LOC mark from 
> 
> Sorry I meant just dmesg foot print. I think before you add anything
> new you first need a construct like apic_printk() with a configurable log level
> with a low default.
> 

Oh right, my bad.

At normal logging levels, the largest output is from stuff like this

Zone PFN ranges:
  DMA          1024 ->   262144
  Normal     262144 ->   262144
early_node_map[3] active PFN ranges
  0:     1024 ->    30719
  0:    32768 ->    65413
  0:    65440 ->    65505

So, that is one line per zone, one line per map entry (that can get
large). There is also lines outputting pages used for memmap, that's
more lines per zone and the DMA zone reserve.

Ok.... it's adding up.

With loglevel at KERN_DEBUG, there can be a very large number of lines
like

Entering add_active_range(0, 1024, 30719) 0 entries of 256 used

I see your point. I'll look into doing something like apic_printk().

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/