From: David Woodhouse <dwmw2@infradead.org>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: torvalds@transmeta.com (Linus Torvalds),
viro@math.psu.edu (Alexander Viro),
linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: [BK-PATCH-2.5] Introduce new VFS inode cache lookup function
Date: Sun, 01 Sep 2002 16:17:41 +0100 [thread overview]
Message-ID: <26631.1030893461@redhat.com> (raw)
In-Reply-To: <E17lCXU-0002zH-00@storm.christs.cam.ac.uk>
aia21@cantab.net said:
> The below ChangeSet against Linus' current BK tree adds a new function
> to the VFS, fs/inode.c::ilookup().
> This is needed in NTFS when writing out inode metadata pages via the
> VM dirty page code paths as we need to know whether there is an active
> inode in icache but we don't want to do an iget() because if the inode
> is not active then there is no need to write it... - I can just skip
> onto the next one instead... - If there is an active inode then I need
> to get the struct inode in order to perform appropriate locking for
> the write out to happen.
Yum. I need similar functionality for JFFS2 garbage collection. When moving
a data node, we currently iget() the inode to which it belongs and update
its in-core extent lists accordingly. If the inode in question wasn't
already present, there's no real need to do that.
--
dwmw2
next prev parent reply other threads:[~2002-09-01 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 18:00 [BK-PATCH-2.5] Introduce new VFS inode cache lookup function Anton Altaparmakov
2002-09-01 15:17 ` David Woodhouse [this message]
2002-09-02 10:02 ` Nikita Danilov
2002-09-03 3:57 ` Jan Harkes
2002-09-03 5:20 ` Anton Altaparmakov
2002-09-03 15:22 ` Jan Harkes
2002-09-03 15:31 ` Anton Altaparmakov
2002-09-03 16:07 ` Jan Harkes
2002-09-03 18:14 ` Daniel Phillips
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=26631.1030893461@redhat.com \
--to=dwmw2@infradead.org \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.