From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: External log size limitations
Date: Sat, 19 Feb 2011 14:33:58 -0600 [thread overview]
Message-ID: <4D602936.10400@hardwarefreak.com> (raw)
In-Reply-To: <20110219100207.GA24537@citd.de>
Matthias Schniedermeyer put forth on 2/19/2011 4:02 AM:
> On 18.02.2011 21:53, Stan Hoeppner wrote:
>> Fist, sorry for the length. I can tend to get windy talking shop. :)
>>
>> Andrew Klaassen put forth on 2/18/2011 2:31 PM:
>>
>>> It's IBM and LSI gear, so I'm crossing my fingers that a Linux install
>>> will be relatively painless.
>>
>> Ahh, good. At least, so far it seems so. ;)
>>
>>> I thought that the filesystem block size was still limited to the kernel
>>> page size, which is 4K on x86 systems.
>>>
>>> http://oss.sgi.com/projects/xfs/
>>>
>>> "The maximum filesystem block size is the page size of the kernel, which
>>> is 4K on x86 architecture."
>>>
>>> Is this no longer true? It would be awesome news if it wasn't.
>>
>> My mistake. It would appear you are limited to the page size, which, as
>> I mentioned, is still 8 KiB for most distros.
>
> You confuse that with STACK-size.
Yes, I did. However...
> The page-size is, and has always been, 4 KiB (on X86).
To bring this back around to the OP's original question, do you agree or
disagree with my assertion that a 64 KiB XFS block size will yield
little if any advantage over a 4 KiB block size, and may in fact have
some disadvantages, specifically with small file random IO?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-19 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 18:54 External log size limitations Andrew Klaassen
2011-02-17 0:32 ` Dave Chinner
2011-02-18 15:26 ` Andrew Klaassen
2011-02-18 19:55 ` Stan Hoeppner
2011-02-18 20:31 ` Andrew Klaassen
2011-02-19 3:53 ` Stan Hoeppner
2011-02-19 10:02 ` Matthias Schniedermeyer
2011-02-19 20:33 ` Stan Hoeppner [this message]
2011-02-19 21:47 ` Emmanuel Florac
2011-02-20 21:14 ` Dave Chinner
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=4D602936.10400@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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 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.