From: Eric Sandeen <sandeen@sandeen.net>
To: yy <yy@xspring.net>, xfs <xfs@oss.sgi.com>
Subject: Re: XFS buffer IO performance is very poor
Date: Wed, 11 Feb 2015 10:08:16 -0600 [thread overview]
Message-ID: <54DB7E70.3060709@sandeen.net> (raw)
In-Reply-To: <tencent_39AFE52BC5E06F89B6B2B3ED@qq.com>
On 2/11/15 1:39 AM, yy wrote:
<snip>
(In addition to Brian's questions):
> XFS format parametes:
>
> #mkfs.xfs -d su=256k,sw=5 /dev/sdb1
>
> #cat /proc/mounts
>
> /dev/sdb1 /data1 xfs rw,noatime,attr2,delaylog,nobarrier,logbsize=256k,sunit=512,swidth=2560,noquota 0 0
>
> #fdisk -ul
> Device Boot Start End Blocks Id System
> /dev/sdb1 128 2929356359 1464678116 83 Linux
so 128*512 = 64k; your partition doesn't start on a 256k stripe unit boundary,
right? Shouldn't it do so?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-11 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 7:39 XFS buffer IO performance is very poor yy
2015-02-11 13:35 ` Brian Foster
2015-02-11 16:08 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-12 5:30 yy
2015-02-12 6:59 yy
2015-02-12 21:04 ` Dave Chinner
2015-02-13 2:20 yy
2015-02-13 13:46 ` Carlos Maiolino
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=54DB7E70.3060709@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=yy@xspring.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.