From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: block sizes > 4K ?? possible w/large page support?
Date: Mon, 11 Jun 2012 09:54:57 -0500 [thread overview]
Message-ID: <4FD606C1.1070103@hardwarefreak.com> (raw)
In-Reply-To: <20120611132932.GA18432@andromeda.usersys.redhat.com>
On 6/11/2012 8:29 AM, Carlos Maiolino wrote:
> The maximum block size of a XFS filesystem is 64kiB. But in linux it's limited
> to the PAGE_SIZE value.
Correct.
> so, on x86 architectures, the maximum block size is
> 4kiB.
Not entirely correct. Since ~1996, 16 years ago, PPro and higher 32bit
CPUs with PSE/PSE36 support pages of 4MB, or 2MB with PAE enabled.
x86-64 CPUs in long mode also support a 2MB page size. But the problem
of internal fragmentation may outweigh the TLB and other benefits of
these very large pages. I'm not an MM dev so I can't elaborate further.
There may be other issues.
> although it could benefit from a 16kiB page size, you'll need to be running an
> operating system which supports this page size value.
And AFAIK the kernel MM team doesn't have x86 2MB pages on their radar.
Or do they?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-11 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 3:21 block sizes > 4K ?? possible w/large page support? Linda A. Walsh
2012-06-11 13:13 ` Stan Hoeppner
2012-06-11 13:29 ` Carlos Maiolino
2012-06-11 14:54 ` Stan Hoeppner [this message]
2012-06-11 16:21 ` Carlos Maiolino
2012-06-11 21:25 ` Stefan Ring
2012-06-11 23:56 ` Dave Chinner
2012-06-12 0:08 ` Dave Chinner
2012-06-12 2:32 ` Eric Sandeen
2012-06-12 17:37 ` Linda A. Walsh
2012-06-12 18:55 ` Eric Sandeen
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=4FD606C1.1070103@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.