lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 20 Mar 2017 10:20:30 -0400
From:   Theodore Ts'o <>
To:     Alexey Lyashkov <>
Cc:     Andreas Dilger <>,
        Artem Blagodarenko <>,
        linux-ext4 <>,
        Yang Sheng <>,
        Zhen Liang <>,
        Artem Blagodarenko <>
Subject: Re: [PATCH] Add largedir feature

On Mon, Mar 20, 2017 at 02:34:31PM +0300, Alexey Lyashkov wrote:
> To make picture clean. OST side is regular FS with 32 directories where a stripe objects is live.
> With current 4G inodes limit each directory will filled with up 100k regular files.
> Files allocated in batch, up to 20k files per batch. Allocated object used on MDT side to make mapping between metadata objects and data for such file.
> I worry about it part, not about MDT. these directories have a large number creations/unlinks and performance degradation started after 3M-5M creations/unlinks.
> With Large dir feature i think this performance problems may deeper.

This makes no sense.  On the Object Store side, if the maximum
directory size is 100k regular files, you're never going to run into
two-levle htree limit, so the presense (or absense) of largedir is
largely irrelevant.  So how can it make the performance problem worse?

						- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ