xfs
[Top] [All Lists]

Re: XFS_IOC_RESVSP64 versus XFS_IOC_ALLOCSP64 with multiple threads

To: Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: XFS_IOC_RESVSP64 versus XFS_IOC_ALLOCSP64 with multiple threads
From: Sam Vaughan <sjv@xxxxxxx>
Date: Tue, 14 Nov 2006 11:31:15 +1100
Cc: Stewart Smith <stewart@xxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20061114002536.GA7846@xxxxxxxxxxxxxxxxxxxxx>
References: <1163381602.11914.10.camel@xxxxxxxxxxxxxxxxxxxxx> <965ECEF2-971D-46A1-B3F2-C6C1860C9ED8@xxxxxxx> <1163390942.14517.12.camel@xxxxxxxxxxxxxxxxxxxxx> <12275452-56ED-4921-899F-EFF1C05B251A@xxxxxxx> <1163395250.14517.38.camel@xxxxxxxxxxxxxxxxxxxxx> <950D2C3E-11AE-4805-9286-65ECD880272D@xxxxxxx> <20061114002536.GA7846@xxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
On 14/11/2006, at 11:25 AM, Chris Wedgwood wrote:

On Tue, Nov 14, 2006 at 11:04:17AM +1100, Sam Vaughan wrote:

Those extents are curiously uniform, all 32kB in size.

O_SYNC writes?

I'm assuming from Stuart's original email that these files weren't written out with write(), but instead pre-allocated using allocsp:

So, this would lead me to try XFS_IOC_ALLOCSP64 - which doesn't have the
"unwritten extents" warning that RESVSP64 does. However, with the two
processes writing the files out, I get heavy fragmentation. Even with a
RESVSP followed by ALLOCSP I get the same result.


<Prev in Thread] Current Thread [Next in Thread>