This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: locale files and page size
- From: Chris Metcalf <cmetcalf at tilera dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Wed, 11 Sep 2013 11:20:26 -0400
- Subject: Re: locale files and page size
- Authentication-results: sourceware.org; auth=none
- References: <Pine dot LNX dot 4 dot 64 dot 1309110136100 dot 18202 at digraph dot polyomino dot org dot uk>
On 9/10/2013 9:52 PM, Joseph S. Myers wrote:
> So: should we simply eliminate this page-alignment optimization completely
> (I rather doubt it makes any significant difference to the cost of loading
> a locale from the archive)
It might be informative to try a quick profile with getpagesize() vs some other large page size-ish constant and see if there is any noticeable difference. If there isn't, I'd suggest just aligning to something cache-line-ish (64, 256, etc) in a platform-independent way and leave it at that. If there is, I'd still suggest just aligning to some fixed "normal" page size like 4K and not worrying about it - I doubt that on architecture with larger default page sizes (like tile) that it would matter that much to be aligned to some large but sub-page-size alignment.
> or should it change to use an
> architecture-independent constant instead of calling getpagesize - or
> should it use an architecture-dependent constant (sufficient for the
> reproducible builds issue) together with a command-line option to change
> the assumed page size for the cross-build case - or should the default
> continue to be as at present, but with such a command-line option for both
> the cross-build and reproducible-build cases?
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com