Hi,
On Fri, Sep 08, 2000 at 12:30:52PM -0600, Andreas Dilger wrote:
> I also just noticed that in ialloc that after ext2_find_first_zero_bit()
> if ext2_set_bit() fails (i.e. the block was stolen from under us), we
> go all the way back to loading the block bitmaps, rather than simply
> calling ext2_find_next_zero_bit() for the same group...
It should be sufficiently rare that you're better off doing that than
increasing the code path length, overall.
> > The subsequent quota update doesn't need serialising, and neither does
> > the group status information if we use atomic types there.
>
> You also need to update the superblock status information, which may be
> the big point of contention.
atomic_t ought to be fine for that.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
