Re: [PATCH] jffs2: implement mount option to configure endianness

[David Woodhouse <dwmw2@infradead.org>]

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

On Thu, 2018-11-08 at 18:01 +0000, Nikunj Kela (nkela) wrote:
>     But we can hypothesise and handwave about it until the cows come home;
>     I'd like to see a real test of whether it actually makes a difference
>     that we care about.
>     
>     If it does, one option might be to just build separate versions of
>     scan.c for each endianness, since that's the critical path we care
>     about.
> 
> I wonder if this feature is really that important that we need to duplicate the drivers.
> Also, it might take some time for me to find some device that I can run the tests with and without this patch.

Hm?

# modprobe mtdram size=16384
# mount -tjffs2 mtd0 /mnt
# cp -av .git /mnt # until it fills up
# umount /mnt
# perf record mount -tjffs2 mtd0 /mnt

On my desktop 'perf' only gets about 12 samples from that, so it's not
ideal. But you can make the mtdram device bigger, use something other
than my shiny new laptop, and use a higher sample frequency from 'perf'
and you should be able to get some vaguely meaningful results.


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]