Make sure you are working with zam on this. zam, check your code into cvs on
its own branch so Chris can take a look.
Hans
Chris Mason wrote:
>
> On Tue, 6 Jun 2000, Andi Kleen wrote:
>
> > On Tue, Jun 06, 2000 at 12:50:37PM +0100, Alan Cox wrote:
> > > > I would have used a global hook (register_memory_pressure_handler())
> > > > Hmm, ok a super block vector would do too, but the global hook would
> > > > be probably useful for other things too (e.g. networking could use it for
> > > > its skb caches). Block device interface has nothing to do with the VFS
> > > > imho (you may be using a different definition of VFS than me tho)
> > >
> > > A notifier chain seems the obvious thing to use for it then ?
> >
>
> This is the probably most important part of the journal infrastructure,
> and Stephen Tweedie and I recently traded plans on how to do it. I
> wanted to get a patch done last week, and I'll try again this week.
>
> We need two things:
>
> 1) a way to reserve and release a pinned page count. This will allow a
> pinned page high watermark so the journaled filesystems can plan nice
> without pinning all the ram.
>
> 2) A memory pressure call back in the address space operations. This
> really does seem more flexible than a call in struct super_operations.
>
> -chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:25 EST