RE: How to measure the RAM read/write performance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----------------------------------------
> From: buyit@xxxxxxx
> To: coolsandyforyou@xxxxxxxxx; kernelnewbies@xxxxxxxxxxxxxxxxx
> Subject: RE: How to measure the RAM read/write performance
> Date: Wed, 27 Feb 2013 22:33:15 +0800
> CC: dhylands@xxxxxxxxx
>
> ________________________________
> > From: coolsandyforyou@xxxxxxxxx
> > Date: Tue, 26 Feb 2013 17:01:54 +0530
> > Subject: How to measure the RAM read/write performance
> > To: kernelnewbies@xxxxxxxxxxxxxxxxx
> > CC: dhylands@xxxxxxxxx
> >
> > Hi All
> > In performance benchmark tools, When we profile read/write timings
> > mostly, those read/writes are done to cache only.
> >
> > I want to measure my DDR(RAM chip) performance.
> > So i want to make sure, every read/write should happen to DDR RAM chip only.
> >
> > How can i achieve this...Any ideas/suggestions...?
>
> try to reserve a large region from bootloader(L4 in Qualcomm platform), let's say it is 10MB continuous physical memory.

sorry, to be accurate, reserve physical memory is done by kernel cmdline, this cmdline parameter can be passed from L4 to kernel, or configed by kernel itself.
the cmdline will be like below:
mem=510M@0 test_region=2M@510M

above example tells kernel you have totally 512MB physical memory, but kernel will only use the first 510MB, the latter 2MB memory is used by you. how to map and use this region depends on you. 

> in kernel, map this region to an continuous virtual region, note that the pgprot should be uncachable since you want to test without cache.

1. use early_param to get the physical start address and size of test_region, or you can just ignore this step and hard code to 510M and 2M for test purpose only.

2. use ioremap_nocache() to map this region to a virtual region. note that this funtion may fail if you are asking a very large vitual memroy region.

> once you configed like this, you can read/write to this vitual region without data cache invovled.
>
> >
> > --
> > With regards,
> > Sandeep Kumar Anantapalli,
> >
> > _______________________________________________ Kernelnewbies mailing
> > list Kernelnewbies@xxxxxxxxxxxxxxxxx
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies 		 	   		  
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux