[Top] [All Lists]

Re: [RFC v2] Unicode/UTF-8 support for XFS

To: Andi Kleen <andi@xxxxxxxxxxxxxx>
Subject: Re: [RFC v2] Unicode/UTF-8 support for XFS
From: Ben Myers <bpm@xxxxxxx>
Date: Tue, 23 Sep 2014 15:45:13 -0500
Cc: Olaf Weber <olaf@xxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, tinguely@xxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140923201540.GB15923@xxxxxxxxxxxxxxxxxx>
References: <20140918195650.GI19952@xxxxxxx> <87lhpbhfgg.fsf@xxxxxxxxxxxxxxxxxxxx> <20140922184145.GH4482@xxxxxxx> <20140922192958.GJ4120@xxxxxxxxxxxxxxxxxx> <54219C17.3090104@xxxxxxx> <20140923201540.GB15923@xxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
Hi Andi,

On Tue, Sep 23, 2014 at 10:15:40PM +0200, Andi Kleen wrote:
> > You only pay the space cost if you use it, similar to the nls tables.
> The way Linux module loading works these things are loaded by default,
> not when someone needs it.
> So no, you (or rather every unfortunate Linux XFS user) would pay it always,
> unless you black list the module or rebuild the kernel.

The suggestion to use symbol_get was made in response to the initial
post of the series.  In my testing the normalization module did not load
until I attempted to mount a filesystem which required it.  Seems to
work ok.

See patch 10, "xfs: implement demand load of utf8norm.ko". 


<Prev in Thread] Current Thread [Next in Thread>