Highmem on PPC?

Mark A. Greer mgreer at mvista.com
Fri Feb 8 10:09:14 EST 2002

Val Henson wrote:

> On Thu, Feb 07, 2002 at 02:53:19PM -0700, Mark A. Greer wrote:
> >
> > Val Henson wrote:
> >
> > > Also, I don't think this was a particularly good test of highmem since
> > > I don't think many bounce buffers were used, or that the kernel had
> > > much reason to map/unmap many highmem pages.  Unfortunately, my SCSI
> > > controller isn't working quite right and I can't test with a hard disk
> > > as a result.  Any ideas for stressing the system harder?
> >
> > You could try lowering max_low_mem.  You can do this by setting "Code
> > maturity level option"/"Prompt for advanced kernel configuration options"
> > and then going under where you selected HIGH_MEM and setting max_low_mem
> > size to something small.
> >
> > It will likely take some trial and error to get it stressed enough.
> > You'll have to start a bunch or processes and look at where they're
> > getting their memory
> See, I don't think that user processes using highmem pages is testing
> highmem much.  So we have user pages mapped by PTE's - what's changed?
> Not a whole lot.  It's when we use bounce buffers in the kernel or ask
> the kernel to map user pages or otherwise trigger the kmap/kunmap code
> that I'm interested in.

I agree.  What I had in mind was causing the kernel to kmap pages for some
reason like to copy user data into the buffer cache of a block device (see
generic_file_write).  I would make a pgm to allocate some mem (like the size
of your lowmem), mlock it down, then fork some processes that do short writes
to a block device or something like that.  I think that would do it.

Did you mentioned that your scsi ctlr or drive was bad?  If so, you'll have to
find some other block device, /dev/ram? maybe??


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

More information about the Linuxppc-dev mailing list