[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <484F45C9.3030804@cn.fujitsu.com>
Date: Wed, 11 Jun 2008 11:26:01 +0800
From: Shen Feng <shen@...fujitsu.com>
To: Andreas Dilger <adilger@....com>
CC: Mingming Cao <cmm@...ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Theodore Tso <tytso@....edu>, sandeen@...hat.com,
linux-ext4@...r.kernel.org
Subject: Re: [PATCH -v2] ext4: Use inode preallocation with -o noextents
Andreas Dilger Wrote:
> On Jun 05, 2008 07:55 -0700, Mingming Cao wrote:
>>> /**
>>> - * ext4_new_blocks_old() -- core block(s) allocation function
>>> + * ext4_orlov_new_blocks() -- core block(s) allocation function
>> what is orlov means? this is core function for non extent based without
>> mballoc block allocation, right?
>
> Orlov is the name of the INODE allocator, not the block allocator. I'm
> not sure there is a name for the block allocator except "old" or "bitmap".
> In the future I suspect we won't want to keep this version at all, using
> the mballoc allocator even for block-mapped files, but it is useful for
> now for performance comparisons.
>
Is that true?
I got the following from the kernel ext4 documentation.
orlov (*) This enables the new Orlov block allocator. It is
enabled by default.
oldalloc This disables the Orlov block allocator and enables
the old block allocator. Orlov should have better
performance - we'd like to get some feedback if it's
the contrary for you.
-Shen Feng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists