linux-ext4 - Re: where is the ext4 git tree ?

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, 26 Jan 2007 13:47:24 -0700
From:	Alex Tomas <alex@...sterfs.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Mingming Cao <cmm@...ibm.com>, coly <colyli@...il.com>,
	linux-ext4@...r.kernel.org
Subject: Re: where is the ext4 git tree ?

On Fri, Jan 26, 2007 at 11:51:19AM -0500, Theodore Tso wrote:
> The first patch series can be found here:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/2.6.20-rc5-ext4-1
> 
> I've included Alex's latest patches which he sent back in December,
> but I haven't gone back before that looking for patches from before.
> If you think there is a patch which should be included that hasn't
> been, please repost it to linux-ext4.  

I'd appreciate a lot review and discussion of mballoc's design.

the most serious change over the last version is preallocation. because
of specific workloads our customers like we have to support multiple
preallocations per inode.

a bit about structures ... every preallocated chunk is described with a
special structure. preallocated space is assigned to logical offset of
a file. the structure is on two lists:
  1) preallocations in a group
  2) preallocations in an inode

before searching blocks, mballoc loads on-disk bitmap and generates:
  1) in-core bitmap, which is copy of on-disk bitmap + all preallocated
     blocks in the group
  2) buddy, which is generated from in-core bitmap

once the both structures are initialized, mballoc finds suitable space
and creates preallocation descriptor, if preallocation is requested.
subsquent allocations find the descriptor via per-inode list using logical
offset as a key and mark block(s) used in on-disk bitmap.

thanks, Alex

-
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