From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH 0/5] Break up "fall back to vmalloc() for large allocations"
Date: Mon, 1 Aug 2011 09:13:13 -0400 [thread overview]
Message-ID: <1312204398-12460-1-git-send-email-tytso@mit.edu> (raw)
In-Reply-To: <A8CDAA23-61C6-4823-ADB1-7D36CBAFC025@whamcloud.com>
This patch series breaks up Andreas and Yu Jian's patch "fall back to
vmalloc() for large allocations" into 5 patches, with the following
changes:
1) I created new helper functions, ext4_kvmalloc(), ext4_kzalloc, and
ext4_kvfree() to simplify the code.
2) Fixed the patch so that online resize would work correctly if
s_group_info and s_group_desc were allocated using vmalloc().
(Yeah, there are other reasons why online resize won't work for
such large allocations, but let's not add to the problems; also,
there's always the possibility that kmalloc might fail for even
for a small allocation.)
3) Fixed many more places in mballoc.c where ext4_msg() would be better
than just printk().
I was waiting for Andreas and/or Yu Jian to resubmit, but since they
didn't, and I wanted these fixes, I decided to break up the patch
myself.
- Ted
Theodore Ts'o (3):
ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree()
ext4: use ext4_kvzalloc()/ext4_kvmalloc() for s_group_desc and
s_group_info
ext4: use ext4_msg() instead of printk in mballoc
Yu Jian (2):
ext4: use EXT4_BAD_INO for buddy cache to avoid colliding with valid
inode #
ext4: prevent memory leaks from ext4_mb_init_backend() on error path
fs/ext4/ext4.h | 3 ++
fs/ext4/mballoc.c | 103 +++++++++++++++++++++++++++++------------------------
fs/ext4/resize.c | 13 ++++---
fs/ext4/super.c | 63 +++++++++++++++++++++-----------
4 files changed, 107 insertions(+), 75 deletions(-)
--
1.7.4.1.22.gec8e1.dirty
next prev parent reply other threads:[~2011-08-01 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 21:40 [PATCH] ext4: fall back to vmalloc() for large allocations Andreas Dilger
2011-07-18 1:25 ` Ted Ts'o
2011-07-18 5:12 ` Andreas Dilger
2011-07-18 11:36 ` Ted Ts'o
2011-08-01 13:13 ` Theodore Ts'o [this message]
2011-08-01 13:13 ` [PATCH 1/5] ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree() Theodore Ts'o
2011-08-02 6:07 ` [PATCH] ext4: use kzalloc in ext4_kzalloc() Mathias Krause
2011-08-03 18:57 ` Ted Ts'o
2011-08-01 13:13 ` [PATCH 2/5] ext4: use ext4_kvzalloc()/ext4_kvmalloc() for s_group_desc and s_group_info Theodore Ts'o
2011-08-01 13:13 ` [PATCH 3/5] ext4: use ext4_msg() instead of printk in mballoc Theodore Ts'o
2011-08-02 3:12 ` Andreas Dilger
2011-08-01 13:13 ` [PATCH 4/5] ext4: use EXT4_BAD_INO for buddy cache to avoid colliding with valid inode # Theodore Ts'o
2011-08-01 13:13 ` [PATCH 5/5] ext4: prevent memory leaks from ext4_mb_init_backend() on error path 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=1312204398-12460-1-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.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;
as well as URLs for NNTP newsgroup(s).