From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
lkml <linux-kernel@vger.kernel.org>,
ext2-devel <Ext2-devel@lists.sourceforge.net>
Subject: Re: [RFC][PATCH] Manage jbd allocations from its own slabs
Date: Wed, 23 Aug 2006 16:34:10 -0700 [thread overview]
Message-ID: <20060823163410.d9af3baa.akpm@osdl.org> (raw)
In-Reply-To: <1156374495.30517.5.camel@dyn9047017100.beaverton.ibm.com>
On Wed, 23 Aug 2006 16:08:15 -0700
Badari Pulavarty <pbadari@us.ibm.com> wrote:
> Hi,
>
> Here is the fix to "bh: Ensure bh fits within a page" problem
> caused by JBD.
>
> BTW, I realized that this problem can happen only with 1k, 2k
> filesystems - as 4k, 8k allocations disable slab debug
> automatically. But for completeness, I created slabs for those
> also.
>
> What do you think ? I ran basic tests and things are fine.
>
Thanks for working on this.
> ...
>
> /*
> + * jbd slab management: create 1k, 2k, 4k, 8k slabs and allocate
> + * frozen and commit buffers from these slabs.
> + *
> + * Reason for doing this is to avoid, SLAB_DEBUG - since it could
> + * cause bh to cross page boundary.
> + */
> +
> +static kmem_cache_t *jbd_slab[4];
> +static const char *jbd_slab_names[4] = {
> + "jbd_1k",
> + "jbd_2k",
> + "jbd_4k",
> + "jbd_8k",
> +};
> +
> +static void journal_destroy_jbd_slabs(void)
> +{
> + int i;
> +
> + for (i=0; i<4; i++) {
> + if (jbd_slab[i])
> + kmem_cache_destroy(jbd_slab[i]);
> + jbd_slab[i] = NULL;
> + }
> +}
> +
> +static int journal_init_jbd_slabs(void)
> +{
> + int i = 0;
> + int retval = 0;
> +
> + for (i=0; i<4; i++) {
> + unsigned long slab_size = 1024 << i;
> + jbd_slab[i] = kmem_cache_create(jbd_slab_names[i],
> + slab_size, slab_size,
> + 0, NULL, NULL);
OK, passing align=slab_size fixes the bug.
> + if (jbd_slab[i] == 0) {
> + journal_destroy_jbd_slabs();
> + retval = -ENOMEM;
> + printk(KERN_EMERG "JBD: no memory for jbd_slab cache\n");
> + goto out;
> + }
> + }
> +out:
> + return retval;
> +}
Do we have to create all four slabs up-front? Perhaps we can defer that
until mount-time, after we have determined the filesystem's block size.
That way, most people's machines will only ever create a single slab cache:
jbd_4k.
> +static int jbd_find_slab_index(size_t size)
> +{
> + int idx = 0;
> +
> + switch (size) {
> + case 1024: idx = 0;
> + break;
> + case 2048: idx = 1;
> + break;
> + case 4096: idx = 2;
> + break;
> + case 8192: idx = 3;
> + break;
> + default: printk("JBD unknown slab size %ld\n", size);
> + BUG();
> + }
> + return idx;
> +}
I'd suggest this function be changed to directly return a kmem_cache_t *.
> +void * jbd_slab_alloc(size_t size, gfp_t flags)
> +{
> + int idx;
> +
> + idx = jbd_find_slab_index(size);
> + return kmem_cache_alloc(jbd_slab[idx], flags | __GFP_NOFAIL);
> +}
> +
> +void jbd_slab_free(void *ptr, size_t size)
> +{
> + int idx;
> +
> + idx = jbd_find_slab_index(size);
> + kmem_cache_free(jbd_slab[idx], ptr);
> +}
Then these become simpler.
next prev parent reply other threads:[~2006-08-23 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 23:08 Badari Pulavarty
2006-08-23 23:34 ` Andrew Morton [this message]
2006-08-24 12:41 ` [Ext2-devel] " Dave Kleikamp
2006-08-25 0:00 ` Badari Pulavarty
2006-08-24 12:29 ` [Ext2-devel] " Dave Kleikamp
2006-08-24 17:12 ` Badari Pulavarty
2006-08-24 18:53 ` Christoph Hellwig
2006-08-24 19:11 ` Badari Pulavarty
2006-08-25 2:24 ` [Ext2-devel] " Theodore Tso
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=20060823163410.d9af3baa.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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
Powered by JetHome