linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Magnus Ahltorp <map@stacken.kth.se>
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
	linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: MM question
Date: Mon, 15 Mar 1999 18:05:03 GMT	[thread overview]
Message-ID: <199903151805.SAA01926@dax.scot.redhat.com> (raw)
In-Reply-To: <ixdn2266t22.fsf@turbot.pdc.kth.se>

Hi,

On 22 Feb 1999 22:13:09 +0100, Magnus Ahltorp <map@stacken.kth.se> said:

> Right now, an Arla inode has some extra information, containing a
> dentry for the cache file. The readpage() function just validates the
> cache information, fills in a struct file (with the ext2 inode) and
> calls ext2's readpage(). The struct page pointer is passed along to
> ext2's readpage() without any modifications.

This sounds like the source of the problem: the Arla inode's readpage
function will not be called if the page cache for the Arla page is
already present.  If you write to the underlying file, it will update
any ext2fs page cache present for the page, but will not touch the Arla
page itself.  You need to call update_vm_cache() against the appropriate
Arla inode for that to happen.  (Ext2 will already call
update_vm_cache() for the ext2fs inode, so the ext2 page cache will
remain consistent internally.)

Of course, you really want to take a step back at this point and work
out if this is really the best way forward, since you just end up
caching things twice if you are not careful...

--Stephen
--
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/

  parent reply	other threads:[~1999-03-15 18:05 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
1999-03-15 18:05     ` Stephen C. Tweedie [this message]
  -- 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=199903151805.SAA01926@dax.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=blah@kvack.org \
    --cc=linux-mm@kvack.org \
    --cc=map@stacken.kth.se \
    /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