From: Deanan <delusion@delusion.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: chatz@melbourne.sgi.com, xfs@oss.sgi.com
Subject: Re: inode64 workaround
Date: Thu, 30 Nov 2006 12:33:35 -0800 [thread overview]
Message-ID: <456F401F.3030902@delusion.com> (raw)
In-Reply-To: <456E67EB.2030008@sandeen.net>
It's a generic 2.6.9 kernel (AFAIK).
I tried the same setting on a different box with SLES 9 SP3 (2.6.5)
which does have rotorstep.
With inode64 I can sustain 235+MB/s on the same array test after test.
When I do not mount with inode64, I get the same results as the 32bit
machine (~100-130MB/s)
Without inode64 plus rotorstep (set to 255), the perfomance improves to
about 140-160MB/s.
Generally the first test is fast and then drops over the next few tests
(even writing as few
as 100 16mb files per test).
Thanks,
Deanan
> Deanan wrote:
>> Thanks. Unfortunately 2.6.9 doesn't have it. :(
>
> Is this rhel4?
>
> You could probably pretty easily add the inode rotor code into the xfs
> modules that you're using, if that's the case.
>
> -Eric
>
>>> This is a sysctl, see sysctl(8).
>>>
>>> It was introduced to XFS in October 2004, I'm not sure if it made
>>> 2.6.9.
>>>
>>> If this doesn't help a little then I'm unsure why you think that
>>> inode64 is
>>> going to solve your problem?
>>>
>>> David
>>>
>>
>>
>
>
prev parent reply other threads:[~2006-11-30 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:27 [PATCH 2/2]xfs_io man page Utako Kusaka
2006-11-29 22:23 ` Nathan Scott
2006-11-29 23:43 ` inode64 workaround Deanan
2006-11-30 0:47 ` David Chatterton
2006-11-30 0:59 ` Deanan
2006-11-30 1:15 ` David Chatterton
2006-11-30 1:37 ` Deanan
2006-11-30 5:11 ` Eric Sandeen
2006-11-30 20:33 ` Deanan [this message]
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=456F401F.3030902@delusion.com \
--to=delusion@delusion.com \
--cc=chatz@melbourne.sgi.com \
--cc=sandeen@sandeen.net \
--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