lkml.org 
[lkml]   [2007]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] trim memory not covered by WB MTRRs
Date
On Wednesday, June 6, 2007 3:57 pm Justin Piszcz wrote:
> On Wed, 6 Jun 2007, Jesse Barnes wrote:
> > On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
> >> Nope, I booted with only netconsole= options. I have a lot of HW
> >> in the box and I guess the buffer is too small. Not sure where to
> >> change it in the kernel. Looking..
> >
> > It's called "kernel log buffer size" and it's in "General setup".
> >
> > Jesse
>
> Did the dmesg output get you what you needed? Why the few KB
> difference?
>
> :)

Yeah, looked at your e820 and your MTRR settings and I think my patch is
doing the right thing (i.e. trimming just the right amount of memory,
leaving you with as much as possible).

The mem= approach though looks slightly off, but I haven't looked at
x86_64's mem= handling to see why. From a high level though, adjusting
end_pfn is the right thing to do, since theoretically mem= could choose
to make holes in your low memory and keep your high memory in the
allocation pools (though it's not generally implemented this way).

Jesse
-
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/

\
 
 \ /
  Last update: 2007-06-07 01:23    [W:0.084 / U:0.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site