[PATCH 1/3] xfs: restrict allocate worker to x86_64
Mark Tinguely
tinguely at sgi.com
Thu Sep 20 12:37:46 CDT 2012
On 09/19/12 16:54, Dave Chinner wrote:
> On Wed, Sep 19, 2012 at 11:31:34AM -0500, tinguely at sgi.com wrote:
>> Restrict the allocation worker to X86_64 machines. This will improve
>> performance on non-X86-64 machines and avoid the AGF buffer hang.
>>
>> Signed-off-by: Mark Tinguely<tinguely at sgi.com>
>
> NACK.
>
> The stack overflow problems that this works around are not limited
> to x86-64. In the past we've seen overflows on i686 (even with 8k
> stacks), s390 and other platforms, so it's not an isolated issue.
>
> It either works or it doesn't - let's not start down the rathole of
> having different code paths and behaviours for different platforms.
>
> Cheers,
>
> Dave.
Well, I was expecting a 4 letter word from Dave on this patch and "NACK"
was surprisingly mild.
When the allocation worker was placed into XFS, even Christoph wanted a
kernel configure switch to be able turn it off.
Dave has already placed a switch in the code that turns it off for over
half of the direct callers xfs_alloc_vextent() because a performance issue.
We are just finding places where it causes serious issues.
This is worker is an "necessary evil" (I think those were Christoph's
review comment). We should limit the evil to where it is necessary.
--Mark.
More information about the xfs
mailing list