From: Christoph Hellwig <hch@infradead.org>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Linus Torvalds <Torvalds@Transmeta.COM>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [PATCH]: reiser4 [5/8] export remove_from_page_cache()
Date: Thu, 31 Oct 2002 16:31:04 +0000 [thread overview]
Message-ID: <20021031163104.A9845@infradead.org> (raw)
In-Reply-To: <15809.22856.534975.384956@laputa.namesys.com>; from Nikita@Namesys.COM on Thu, Oct 31, 2002 at 07:24:40PM +0300
On Thu, Oct 31, 2002 at 07:24:40PM +0300, Nikita Danilov wrote:
> Reiser4 stores meta-data in a huge balanced tree. This tree is kept
> (partially) in the page cache. All pages in this tree are attached to
> "fake" inode. Sometimes you need to remove node from the tree. At this
> moment page has to be removed from the fake inode mapping.
What about chaing truncate_inode_pages to take an additional len
argument so you don't have to remove all pages past an offset?
>
> Other file systems don't need remove_from_page_cache() because they only
> store in the page cache data (and remove_from_page_cache() is called by
> truncate()) and meta data that are never explicitly deleted (like
> directory content in ext2).
Sorry, but that's wrong. XFS does use the pagecache for all metadata and JFS
for all but the superblock (which is never changed durin use)
next prev parent reply other threads:[~2002-10-31 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:03 [PATCH]: reiser4 [5/8] export remove_from_page_cache() Nikita Danilov
2002-10-31 16:18 ` Christoph Hellwig
2002-10-31 16:24 ` Nikita Danilov
2002-10-31 16:31 ` Christoph Hellwig [this message]
2002-10-31 16:45 ` Nikita Danilov
2002-10-31 16:58 ` Christoph Hellwig
2002-10-31 17:04 ` Nikita Danilov
2002-10-31 17:12 ` Christoph Hellwig
2002-10-31 17:33 ` Andreas Dilger
2002-10-31 18:25 ` Nikita Danilov
2002-10-31 20:17 ` Ragnar Kjørstad
2002-10-31 18:57 ` Linus Torvalds
2002-11-01 21:56 ` Andreas Dilger
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=20021031163104.A9845@infradead.org \
--to=hch@infradead.org \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=Torvalds@Transmeta.COM \
/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