From: Theodore Ts'o <tytso@mit.edu>
To: Artem Blagodarenko <artem.blagodarenko@gmail.com>
Cc: linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca,
alexey.lyashkov@gmail.com, Yang Sheng <yang.sheng@intel.com>,
Artem Blagodarenko <artem.blagodarenko@seagate.com>
Subject: Re: [PATCH] Add largedir feature
Date: Sat, 29 Apr 2017 20:59:53 -0400 [thread overview]
Message-ID: <20170430005953.m74yjettitj7mzr6@thunk.org> (raw)
In-Reply-To: <1489657877-34478-1-git-send-email-artem.blagodarenko@seagate.com>
On Thu, Mar 16, 2017 at 05:51:17AM -0400, Artem Blagodarenko wrote:
> From: Artem Blagodarenko <artem.blagodarenko@gmail.com>
>
> This INCOMPAT_LARGEDIR feature allows larger directories to be created
> in ldiskfs, both with directory sizes over 2GB and and a maximum htree
> depth of 3 instead of the current limit of 2. These features are needed
> in order to exceed the current limit of approximately 10M entries in a
> single directory.
>
> Signed-off-by: Yang Sheng <yang.sheng@intel.com>
> Signed-off-by: Artem Blagodarenko <artem.blagodarenko@seagate.com>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2017-04-30 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 9:51 [PATCH] Add largedir feature Artem Blagodarenko
2017-03-16 21:44 ` Andreas Dilger
2017-03-17 6:15 ` Alexey Lyashkov
2017-03-17 20:51 ` Andreas Dilger
2017-03-18 8:16 ` Alexey Lyashkov
2017-03-18 16:29 ` Theodore Ts'o
2017-03-18 17:17 ` Alexey Lyashkov
2017-03-19 0:39 ` Theodore Ts'o
2017-03-19 4:19 ` Alexey Lyashkov
2017-03-19 6:13 ` Andreas Dilger
2017-03-19 5:38 ` Andreas Dilger
2017-03-19 13:34 ` Theodore Ts'o
2017-03-19 23:54 ` Andreas Dilger
2017-03-20 11:34 ` Alexey Lyashkov
2017-03-20 14:20 ` Theodore Ts'o
2017-03-21 15:38 ` Andreas Dilger
2017-03-20 11:42 ` Theodore Ts'o
2017-04-30 0:59 ` Theodore Ts'o [this message]
2017-05-01 18:58 ` Eric Biggers
2017-05-01 23:39 ` Andreas Dilger
2017-05-02 2:44 ` Theodore Ts'o
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=20170430005953.m74yjettitj7mzr6@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=alexey.lyashkov@gmail.com \
--cc=artem.blagodarenko@gmail.com \
--cc=artem.blagodarenko@seagate.com \
--cc=linux-ext4@vger.kernel.org \
--cc=yang.sheng@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).