[Top] [All Lists]

Re: Odd pagebuf message

To: Jens Axboe <axboe@xxxxxxx>
Subject: Re: Odd pagebuf message
From: Steve Lord <lord@xxxxxxx>
Date: 17 Dec 2001 09:08:56 -0600
Cc: Eric Sandeen <sandeen@xxxxxxx>, David Chambers <davidc@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20011217110745.GH4587@suse.de>
References: <200112161757.fBGHvPW21023@pinga.salk.edu> <Pine.LNX.4.33.0112161927200.12284-100000@chuckle.americas.sgi.com> <20011217110745.GH4587@suse.de>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Mon, 2001-12-17 at 05:07, Jens Axboe wrote:
> On Sun, Dec 16 2001, Eric Sandeen wrote:
> > Congratulations, you appear to be the world's first user of the
> > pre-allocated buffer head pool in pagebuf!  :)
> > 
> > when pagebuf initializes, it sets aside a handful of buffer heads to use
> > in "emergency" situations, i.e. if it tries to allocate a buffer head and
> > fails.  If this happens, it takes one from this pre-allocated pool
> > instead.  If normal allocation fails, _and_ the pre-allocated pool is
> > empty, that thread will sleep until buffer heads get replaced in the
> > pre-allocated pool - this is what happened to you.  The thread gets woken
> > up and picks up where it left off as soon as it is able to get a
> > buffer head allocated from the pool.
> BTW, in your 2.5 tree please drop such private pre-allocations and use
> the mempool_* interface. bio/bio_vec allocations and highmem are already
> using them :-)

It's already gone Jens.



Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx

<Prev in Thread] Current Thread [Next in Thread>