Chris Mason wrote:
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Hans Reiser
> >
> > "Stephen C. Tweedie" wrote:
> >
> > > Hi,
> > >
> > > On Tue, 12 Oct 1999 03:14:03 +0400, Hans Reiser <[EMAIL PROTECTED]> said:
> > >
> > > >> Hans, you didn't mention a journal call that happens on sync, or
> > > >> sync_old_buffers...
> > >
> > > > I see two issues: how to respond to memory pressure, and how to sync.
> > > > I'll let you articulate our sync needs.
> > >
> > > There are actually two separate memory pressure concerns.
> >
> > > The first is
> > > how to clear out some dirty, pinned buffers when we need to free up some
> > > memory, and try_to_free_buffers/bdflush are the main mechanisms involved
> > > right now.
> > >
> > > With journaling, however, we have a new problem. We can have large
> > > amounts of dirty data pinned in memory, but we cannot actualy write
> > > that data to disk without first allocating more memory.
> >
> > Trivia: I don't think this is a feature of journaling, but rather
> > a feature of a
> > particular implementation of journaling. Chris will correct me
> > if I err, but
> > Chris's journaling doesn't have this property.
> >
>
> It didn't before async commits, but it does now.
I need to read that code..... I haven't read the journaling code since I last
sent you my comments on it, and I you have changed a lot.
Hans
--
Get Linux (http://www.kernel.org) plus ReiserFS
(http://devlinux.org/namesys). If you sell an OS or
internet appliance, buy a port of ReiserFS! If you
need customizations and industrial grade support, we sell them.
