Subject: Memory Usage Growth in File access

From: "s.deepak" <[email-masked]>
Date: Mon, 2 May 2005 12:22:39 +0530

Hi All,

I am  facing an issue in file operation, when we read/write continuously to  a large file in our  ppc 405 based device , memory usage shown in /proc/meminfo   increases by the number of bytes accessed.And after closing the application also the memory used is not released and  it goes to cached memory .
We are using 2.4.20 kernel in our device.We are not sure whether the /proc/meminfo shows the erroneous output or the file read/write routines got any problem.
Can anyone suggest me some idea how to trace out the problem.

I have given the sample code  below.
The memory consumption grows and it takes about 10 MB memory space [10000 * 1024] when i run the below given code.
When i look into /proc/meminfo the free memory is reduced by 10 MB and Cache Memory & Used memory is increased by 10 mb after running this application.
When i run the below given code first time the memory grows,when  i run succesively it doesn't grow again , may be using the already taken memory.

int main()
{

FILE *fp;

unsigned long int i;
unsigned char data[1024];

fp=fopen("test.txt","r");
for(i=0;i<10000;i++)
{

      fread(data,1024,1,fp);
}
fclose(fp);
}

With Thanks & Regards,
Deepak S

-- 
This message contains information from GDA Technologies LTD  and affiliates, and is intended for the sole use of the individual and entity to whom it is addressed. It may contain information, including any attachments, that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this electronic transmission in error, please notify the sender immediately by a "reply to sender only" message and destroy all electronic and hard copies of the communication, including attachments.
This message was scanned for spam and viruses by BitDefender.