On Tue, Oct 22 2002, Randy.Dunlap wrote:
> On Tue, 22 Oct 2002, Jens Axboe wrote:
>
> | On Tue, Oct 22 2002, Suparna Bhattacharya wrote:
> | > On Mon, 21 Oct 2002 19:43:20 +0530, Christoph Hellwig wrote:
> | >
> | >
> | > >> +
> | > >> + if ((dump_bio = kmalloc(sizeof(struct bio), GFP_KERNEL)) == NULL) { +
> | > >> DUMP_PRINTF("Cannot allocate bio\n"); + retval = -ENOMEM;
> | > >> + goto err2;
> | > >> + }
> | > >
> | > > Shouldn't you use the generic bio allocator?
> | > >
> | >
> | > Not sure that this should come from the bio mempool. Objects
> | > allocated from the mem pool are expected to be released back to
> | > the pool within a reasonable period (after i/o is done), which is
> | > not quite the case here.
> | >
> | > Dump preallocates the bio early when configured and holds on to
> | > it all through the time the system is up (avoids allocs at
> | > actual dump time). Doesn't seem like the right thing to hold
> | > on to a bio mempool element that long.
> |
> | Definitely, one must not use the bio pool for long term allocations.
>
> "must not" ?
Yes
> what happens if one does do that? [not suggesting doing that]
Well, the whole concept behind mempool and deadlock-free allocation
while doing io, builds on that if slab allocation fails we fall back to
a private pool. If allocation from the private pool also fails, then we
_know_ we have io in progress that will finish "shortly". This is what
makes it safe to sleep on the private pool. Once you start doing long
term allocations from the bio pool, we can no longer make this
guarentee.
-- Jens Axboe- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:58 EST