linux-ext4 - Re: [PATCH] ext4: Enable delalloc and mballoc by default.

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] [day] [month] [year] [list]

Message-ID: <20071024225935.GI26078@webber.adilger.int>
Date:	Wed, 24 Oct 2007 16:59:35 -0600
From:	Andreas Dilger <adilger@....com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: Enable delalloc and mballoc by default.

On Oct 24, 2007  16:15 -0500, Eric Sandeen wrote:
> Andreas Dilger wrote:
> > It is useful to be able to mount w/o extents/delalloc/mballoc for perf
> > testing and functional testing of the block-mapped file path in ext4.
> > Also, some users might want the ability to use features of ext4 w/o
> > the incompatibility of extents.
> 
> Right, I understand the reason for noextents, nodelalloc, nomballoc.
> Above, I ask what is the point of having the *defaults* (extents,
> delalloc, mballoc) as mount options?

Partly for symmetry, and also to be able to override any "no*" options
that might have been specified previously (e.g. in some script that the
user doesn't directly control, but can pass additional options to).

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

-
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