lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 6 Jun 2008 00:16:16 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Andreas Dilger <adilger@....com>
Cc:	Mingming Cao <cmm@...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

On Thu, Jun 05, 2008 at 12:24:55PM -0600, 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".

What do you suggest to rename it as ?  I actually got the name from
http://lwn.net/Articles/14633/. But since the old allocator the block
location depends more closely on where the inodes are place i guess we
can name even the block as orlov allocator.


> 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.
> 

The patch which is marked in the subject is exactly doing that.


-aneesh
--
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