From: Benjamin Schindler <bschindler@inf.ethz.ch>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com
Subject: Re: xfs performance problem
Date: Sun, 1 May 2011 18:56:03 +0200 [thread overview]
Message-ID: <4DBD90A3.6000101@inf.ethz.ch> (raw)
In-Reply-To: <201104291828.46420.Martin@lichtvoll.de>
Hi
On 29.04.2011 18:28, Martin Steigerwald wrote:
> sorry, forgot to cc.
>
> Am Mittwoch, 27. April 2011 schrieb Dave Chinner:
>> On Tue, Apr 26, 2011 at 09:44:04PM +0200, Benjamin Schindler wrote:
>>> Hi
>>>
>>> Since upgrading to newer kernels I have serious problems with xfs
>>> performance on my root fs.
>>> It runs on a software raid 0 with 2 disks. On the same two disks,
>>> there are two more partitions running a software raid-1 with ext3.
>>> On the ext3 system, I have no issue, so I assume the drives are
>>> fine.
>>> But on the xfs filesystem, extracting a linux kernel archive takes 5
>>> minutes or more, running ldconfig similarily long. The harddrives are
>>> sata-2.
>>> I'm running gentoo linux with kernel 2.6.38-gentoo-r1. I'm attaching
>>> the kernel config but I guess more info is needed - just let me know
>>> what is needed.
>>
>> more than likely your problem is that barriers have been enabled for
>> MD/DM devices on the new kernel, and they aren't on the old kernel.
>> XFS uses barriers by default, ext3 does not. Hence XFS performance
>> will change while ext3 will not. Check dmesg output when mounting
>> the filesystems on the different kernels.
>
> But didn't 2.6.38 replace barriers by explicit flushes the filesystem has to
> wait for - mitigating most of the performance problems with barriers?
>
Well, that doesn't seem to work then may be? As always, I'm willing to
do testing and provide info if required
Cheers
Benjamin
p.s. please keep the cc
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-05-01 16:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 16:28 xfs performance problem Martin Steigerwald
2011-04-29 19:51 ` Peter Grandi
2011-05-01 16:56 ` Benjamin Schindler [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-26 19:44 Benjamin Schindler
2011-04-26 22:12 ` Stan Hoeppner
2011-04-26 23:23 ` Benjamin Schindler
2011-04-26 23:59 ` Benjamin Schindler
2011-04-29 15:00 ` Peter Grandi
2011-04-30 20:36 ` Michael Monnerie
2011-05-01 8:49 ` Dave Chinner
2011-05-01 14:38 ` Peter Grandi
2011-05-01 15:08 ` Peter Grandi
2011-05-01 15:32 ` Michael Monnerie
2011-05-01 17:04 ` Peter Grandi
2011-05-02 2:50 ` Dave Chinner
2011-05-02 20:10 ` Emmanuel Florac
2011-05-01 13:33 ` Peter Grandi
2011-05-01 16:32 ` Peter Grandi
2011-04-27 7:55 ` Michael Weissenbacher
2011-04-27 8:09 ` Benjamin Schindler
2011-04-27 2:35 ` Dave Chinner
2011-04-29 16:27 ` Martin Steigerwald
2011-05-01 8:52 ` Dave Chinner
2011-05-01 16:55 ` Christoph Hellwig
2011-05-01 18:24 ` Markus Trippelsdorf
2011-05-02 10:14 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DBD90A3.6000101@inf.ethz.ch \
--to=bschindler@inf.ethz.ch \
--cc=Martin@lichtvoll.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox