linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: linux-fsdevel@vger.kernel.org
Subject: question on bmap
Date: Wed, 22 Jan 2003 23:15:14 +0800	[thread overview]
Message-ID: <3E2EB582.5050005@shaolinmicro.com> (raw)

Hi all,

I am writing a persistent disk cache for a network file system. Is it 
true to use bmap() plus some buffer head ops, is generally faster than 
readpage() and commit_write() paths? As I know the buffer head has a 
reference to the page, that means in terms of memory consumption, they 
are the same (please clarify)?? Not sure which is better.. it seems bmap 
is lower level, but I'm not sure is there any equivalent code like 
grab_cache_page() and read_cache_page() so that I can find so 
in-page_cache pages to save some I/O time. Please advice on usage and 
potential pitfalls. Thanks for any comments.

regards,
David Chow


                 reply	other threads:[~2003-01-22 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E2EB582.5050005@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).