All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: lvm and locales memory issue
Date: Tue, 23 Feb 2010 17:56:22 +0100	[thread overview]
Message-ID: <4B8408B6.4080303@redhat.com> (raw)
In-Reply-To: <20100223162842.GC2817@tyan-ft48-01.lab.bos.redhat.com>

On 23.2.2010 17:28, Jakub Jelinek wrote:
> On Tue, Feb 23, 2010 at 04:17:39PM +0100, Zdenek Kabelac wrote:
>> It looks like cs_CZ.utf8/LC_MESSAGES/SYS_LC_MESSAGES  is just 59 bytes.
>> There is something seriously wrong with the current glibc optimalization to
>> have 100MB locked into memory if you want to use 59 bytes from this file....
> 
> LC_MESSAGES contains just yesstr/nostr definition, nothing else.
> But guess your application isn't asking just for LC_MESSAGES category...

But that's exactly what we actually need for our lvm.
Translated error messages...

>> Looking at the size of /usr/share/i18n/locales/cs_CZ - one may start to wonder
>> why Czech locales are defining collates for arabic latin and other 'related'
>> laguages, while in German there is simple 'copy "iso14651_t1"'
> 
> iso14651_t1 defines collation for all kinds of charsets, ideally cs_CZ
> should just include that file too and tweak afterwards for the differences
> Czech ordering requires.

And where is the problem to handle that this way ?


>> Another note could be - Ubuntu does not even use locale-archive file and uses
>> locales on per file basis - so now I'm getting curious, where are the tests,
> 
> Not everything Ubuntu does is necessarily a good idea.
> 
>> that proves that Fedora gets some measurable performance advantage?

> 
> Try something trivial, like:
> #include <locale.h>

Yeah - typical real world application...


Anyway all we want to achive here is - to have a choice - if application is
using mlockall() it should be able to select less memory demanding way of
handling locales - whole code is already there and imho needs just a little
tweaking around.

Thus glibc could still handle millions of setlocale switches per second for
typical Fedora user which surely appreciate this worthy optimization for 100MB
disk space - but if the application needs - it should be able to select a
method - which allow only thousands of switches - but will fit into few
hundreds kb of memory space for mlockall().

Zdenek



  parent reply	other threads:[~2010-02-23 16:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  9:19 lvm and locales memory issue Zdenek Kabelac
2010-02-18 12:48 ` Milan Broz
2010-02-18 13:26   ` Zdenek Kabelac
2010-02-19 16:11     ` Zdenek Kabelac
2010-02-19 16:30       ` Alasdair G Kergon
2010-02-22 10:55         ` Zdenek Kabelac
2010-02-22 13:16           ` Zdenek Kabelac
2010-02-22 18:11             ` Alasdair G Kergon
2010-02-22 18:23               ` Jakub Jelinek
2010-02-22 18:51                 ` Alasdair G Kergon
2010-02-22 19:05                   ` Jakub Jelinek
2010-02-23  8:52                 ` Zdenek Kabelac
2010-02-23  9:15                   ` Jakub Jelinek
2010-02-23  9:14                     ` Zdenek Kabelac
2010-02-23  9:45                       ` Jakub Jelinek
2010-02-23 10:12                         ` Zdenek Kabelac
2010-02-23 13:07                     ` Zdenek Kabelac
2010-02-23 15:17                   ` Zdenek Kabelac
2010-02-23 16:28                     ` Jakub Jelinek
2010-02-23 16:53                       ` Alasdair G Kergon
2010-02-23 16:56                       ` Zdenek Kabelac [this message]
2010-02-24  9:39                       ` Zdenek Kabelac

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=4B8408B6.4080303@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=lvm-devel@redhat.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.