linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "s.deepak" <s.deepak@gdatech.co.in>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Memory Usage Growth in File access
Date: Mon, 02 May 2005 12:28:15 +0200	[thread overview]
Message-ID: <20050502102820.2024CC1510@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 02 May 2005 12:22:39 +0530." <02cb01c54ee3$87e93ec0$4000a8c0@DeepakS>

In message <02cb01c54ee3$87e93ec0$4000a8c0@DeepakS> you wrote:
>
> 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 .

Welcome to the world of efficient use of resources.

What you see is perfectly normal behaviour and  one  of  the  reasons
that LInux provides excellent performance.

> Can anyone suggest me some idea how to trace out the problem.

There is no problem. What you see is normal the way it  was  designed
to work.

> 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.

Indeed. Also if you have a way to  trace  accesses  to  your  storage
media  you  will see that the secondrun needs much less accesses, and
is faster, too.

Welcome to Unix.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Today is the yesterday you worried about tomorrow.

      reply	other threads:[~2005-05-02 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  6:52 Memory Usage Growth in File access s.deepak
2005-05-02 10:28 ` Wolfgang Denk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050502102820.2024CC1510@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=s.deepak@gdatech.co.in \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).