From: Theodore Tso <tytso@mit.edu>
To: Michael Rubin <mrubin@google.com>
Cc: Curt Wohlgemuth <curtw@google.com>, linux-ext4@vger.kernel.org
Subject: Re: Use of kmalloc vs vmalloc in ext4?
Date: Sat, 25 Apr 2009 22:12:20 -0400 [thread overview]
Message-ID: <20090426021220.GB10248@mit.edu> (raw)
In-Reply-To: <20090425033955.GF13608@mit.edu>
On Fri, Apr 24, 2009 at 11:39:55PM -0400, Theodore Tso wrote:
> P.S. What sort of flex_bg size are you using?
>
> EXT4-fs: not enough memory for 8198 flex groups
> EXT4-fs: unable to initialize flex_bg meta info!
>
> Modern e2fsprogs default to using 16 block groups per flex_bg, which
> means 8198 flex groups is a little over 16 TB --- which the mainline
> e2fsprogs doesn't support yet. You wouldn't be using a smaller
> flex_bg size for some reason, are you?
Oh, never mind. I didn't realize this last night, but we allocate
sbi->s_flex_counts so it is big enough in case the filesystem gets
resized to the maximum size. So that's why it was trying to allocate
that many flex groups. On the other hand, it means that it's much
more likely for us to need the extra memory.
- Ted
prev parent reply other threads:[~2009-04-26 2:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 14:32 Use of kmalloc vs vmalloc in ext4? Curt Wohlgemuth
2009-04-06 6:45 ` Michael Rubin
2009-04-06 9:33 ` Andreas Dilger
2009-04-25 3:00 ` [PATCH] ext4: Fallback to vmalloc if kmalloc can't allocate s_flex_groups array Theodore Ts'o
2009-04-25 3:28 ` Eric Sandeen
2009-04-25 3:57 ` Theodore Tso
2009-04-25 3:07 ` Use of kmalloc vs vmalloc in ext4? Theodore Tso
2009-04-25 3:39 ` Theodore Tso
2009-04-26 2:12 ` Theodore Tso [this message]
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=20090426021220.GB10248@mit.edu \
--to=tytso@mit.edu \
--cc=curtw@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mrubin@google.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).