Alexander Viro wrote:
> i_nlink is 0 (at the moment of last iput(), that is). Otherwise it is
> thrown out only when the memory pressure comes. In any case
> ->clear_inode() is called before releasing the thing. Moreover, there is a
Excellent, that's what I'm looking for
> > I am interested in keeping inode data either in the inode cache, OR the
> > backing store, but not both.
>
> Details, please. If you are talking about procfs - keep in mind that we
> may have multiple mounts.
shmfs. If data is in the inode cache, then ideally an additional copy
should not be in VM...
Thanks,
Jeff
--
Jeff Garzik | Just once, I wish we would encounter
Building 1024 | an alien menace that wasn't immune to
MandrakeSoft, Inc. | bullets. -- The Brigadier, "Dr. Who"
