From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Shields <mshields@google.com>
Cc: rdunlap@xenotime.net, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] Doc fix: ext2 can only have 32,000 subdirs, not 32,768.
Date: Wed, 27 May 2009 17:20:45 -0700 [thread overview]
Message-ID: <20090527172045.f33b0b49.akpm@linux-foundation.org> (raw)
In-Reply-To: <63a2e74f0905181213r54a2d8b2tb7dcecd177d474c2@mail.gmail.com>
On Mon, 18 May 2009 12:13:51 -0700
Michael Shields <mshields@google.com> wrote:
> ext2.txt says that dirs can have 32,768 subdirs, but the actual value
> of EXT2_LINK_MAX is 32000.
> ext3 is the same, but the doc does not mention it. __One of ext4's
> features is to "fix 32000 subdirectory limit".
>
> --- linux-2.6.29.3/Documentation/filesystems/ext2.txt.orig 2009-05-08
> 15:47:21.000000000 -0700
> +++ linux-2.6.29.3/Documentation/filesystems/ext2.txt 2009-05-18
> 12:03:58.000000000 -0700
> @@ -322,7 +322,7 @@ an upper limit on the block size imposed
> __so 8kB blocks are only allowed on Alpha systems (and other architectures
> __which support larger pages).
>
> -There is an upper limit of 32768 subdirectories in a single directory.
> +There is an upper limit of 32000 subdirectories in a single directory.
>
> __There is a "soft" upper limit of about 10-15k files in a single directory
> __with the current linear linked-list directory implementation. __This limit
> --
The patch is wordwrapped and has weird non-ascii characters in the
changelog text. I fixed all that up. Please fix your email client for
future patches.
Please include a Signed-off-by:, as described in
Documentation/SubmittingPatches, thanks.
next prev parent reply other threads:[~2009-05-28 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 19:13 [PATCH] Doc fix: ext2 can only have 32,000 subdirs, not 32,768 Michael Shields
2009-05-28 0:20 ` Andrew Morton [this message]
2009-05-30 11:37 ` Pavel Machek
2009-05-31 0:13 ` Andrew Morton
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=20090527172045.f33b0b49.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshields@google.com \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.org \
/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