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]
Message-Id: <1248210485.18500.2.camel@bobble.smo.corp.google.com>
Date:	Tue, 21 Jul 2009 14:08:05 -0700
From:	Frank Mayhar <fmayhar@...gle.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Curt Wohlgemuth <curtw@...gle.com>, Xiang Wang <xiangw@...gle.com>,
	linux-ext4@...r.kernel.org
Subject: Re: Using O_DIRECT in ext4

On Tue, 2009-07-21 at 11:38 -0500, Eric Sandeen wrote:
> Curt Wohlgemuth wrote:
> > On Mon, Jul 20, 2009 at 8:41 PM, Eric Sandeen<sandeen@...hat.com> wrote:
> >> Xiang Wang wrote:
> 
> >>> For comparison, I did the same experiment on an ext2 partition,
> >>> resulting in each file having only 1 extent.
> >> Interestinng, not sure I would have expected that.
> > 
> > Same with us; we're looking into more variables to understand it.
> 
> To be more clear, I would not have expected ext2 to deal well with it
> either, is more what I meant ;)  I'm not terribly surprised that ext4
> gets fragmented.

Ext2 deals with it via the block reservation code added some time ago.
It turns out it works pretty well for this case.  Ext4, of course,
doesn't use the block reservation code.
-- 
Frank Mayhar <fmayhar@...gle.com>
Google, 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ