linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Shen Feng <shen@cn.fujitsu.com>
Cc: Mingming Cao <cmm@us.ibm.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Theodore Tso <tytso@mit.edu>,
	sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH -v2] ext4: Use inode preallocation with -o noextents
Date: Thu, 12 Jun 2008 03:34:31 -0600	[thread overview]
Message-ID: <20080612093431.GZ3726@webber.adilger.int> (raw)
In-Reply-To: <484F45C9.3030804@cn.fujitsu.com>

On Jun 11, 2008  11:26 +0800, Shen Feng wrote:
> 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.

The documentation is incorrect then.  The Orlov allocator is for inodes:

ialloc.c:
/*
 * Orlov's allocator for directories.
 
struct inode *ext3_new_inode(handle_t *handle, struct inode * dir, int mode)
{
        if (S_ISDIR(mode)) {
		if (test_opt (sb, OLDALLOC))
			group = find_group_dir(sb, dir);
		else
			group = find_group_orlov(sb, dir);


Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2008-06-12  9:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 20:34 [PATCH -v2] ext4: Use inode preallocation with -o noextents Aneesh Kumar K.V
2008-06-04  2:23 ` Theodore Tso
2008-06-04  4:01   ` Aneesh Kumar K.V
2008-06-05  3:22     ` Theodore Tso
2008-06-05  8:43       ` Aneesh Kumar K.V
2008-06-05 14:55         ` Mingming Cao
2008-06-05 18:24           ` Andreas Dilger
2008-06-05 18:46             ` Aneesh Kumar K.V
2008-06-06 21:33             ` Mingming Cao
2008-06-11  3:26             ` Shen Feng
2008-06-12  9:34               ` Andreas Dilger [this message]
2008-06-12 13:41                 ` Eric Sandeen
2008-06-11  3:44           ` Shen Feng
2008-06-16  3:41           ` Shen Feng
2008-06-17  9:42             ` Shen Feng
2008-06-17 10:48               ` Aneesh Kumar K.V
2008-06-18  1:43                 ` Shen Feng
2008-06-05 15:37         ` Theodore Tso
2008-06-05 18:28           ` Andreas Dilger
2008-06-05 19:12             ` Aneesh Kumar K.V
2008-06-05 20:58               ` Andreas Dilger
2008-06-06 16:26           ` Aneesh Kumar K.V

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080612093431.GZ3726@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=shen@cn.fujitsu.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).