From: Kevin Puetz <puetzk@puetzk.org>
To: linux-kernel@vger.kernel.org
Subject: Re: VM disk cache behavior.
Date: Tue, 08 Feb 2005 23:03:13 -0600 [thread overview]
Message-ID: <cuc5fo$7r5$1@sea.gmane.org> (raw)
In-Reply-To: 20050209003754.GA7298@hexapodia.org
Andy Isaacson wrote:
> Most likely is that your app isn't behaving in a cache-friendly way. If
> your file will fit in memory, just fault it in sequentially (wc -l file)
> and then your app should cook. If you're not going to fit in memory,
> the vm caching will probably only help if you have some reuse; you could
> develop a pre-faulter to get your IO started ahead of time, but that's
> generally nontrivial.
Of course, what's non-trivial is predicting your upcoming I/O pattern
(unless it's not actually random at all, just messy). Calling madvise to
prefault it is pretty easy if you actually do know what you'll want in the
near future.
prev parent reply other threads:[~2005-02-09 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 17:06 VM disk cache behavior jon ross
2005-02-08 17:18 ` Robert Love
2005-02-08 20:07 ` Chris Wedgwood
2005-02-09 0:37 ` Andy Isaacson
2005-02-09 5:03 ` Kevin Puetz [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='cuc5fo$7r5$1@sea.gmane.org' \
--to=puetzk@puetzk.org \
--cc=linux-kernel@vger.kernel.org \
/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