From: Magnus Ahltorp <map@stacken.kth.se>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: linux-mm@kvack.org
Subject: Re: MM question
Date: 24 Feb 1999 18:55:33 +0100 [thread overview]
Message-ID: <ixdbtij8z56.fsf@turbot.pdc.kth.se> (raw)
In-Reply-To: "Benjamin C.R. LaHaise"'s message of "Wed, 24 Feb 1999 12:36:11 -0500 (EST)"
> Okay, you probably don't want to implement readpage, just read and write,
> so your read will look like:
>
> This will make your inodes relatively lightweight, and avoid having in
> memory pages attached to your inode which would be duplicates of those
> attached to the ext2 inode.
Doesn't this mean that the read functions will be called every time
something has to be read? What about mmap?
> Readpage is called by generic_file_read and page fault handlers to pull
> the page into the page cache. In the case of writing, you need to update
> the page cache, as well as commit the write to whatever backstore is used.
> Since you've got the entire file cached (right?), just making use of the
> ext2 inode's read & write will keep the cache coherent and reduce the
> amount work you need to do.
At the moment, we do whole file caching, but that might change in the
future.
/Magnus
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-02-24 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-21 19:53 Magnus Ahltorp
1999-02-21 21:34 ` Benjamin C.R. LaHaise
1999-02-22 21:13 ` Magnus Ahltorp
1999-02-24 17:36 ` Benjamin C.R. LaHaise
1999-02-24 17:55 ` Magnus Ahltorp [this message]
1999-03-15 18:05 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
1999-02-16 2:30 Jason Titus
1999-02-18 15:06 ` Stephen C. Tweedie
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=ixdbtij8z56.fsf@turbot.pdc.kth.se \
--to=map@stacken.kth.se \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.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