From: Theodore Tso <tytso@mit.edu>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
akpm@osdl.org, lkml <linux-kernel@vger.kernel.org>,
ext2-devel <Ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] [RFC][PATCH] Manage jbd allocations from its own slabs
Date: Thu, 24 Aug 2006 22:24:05 -0400 [thread overview]
Message-ID: <20060825022405.GA3692@thunk.org> (raw)
In-Reply-To: <44EDF9DD.3040904@us.ibm.com>
On Thu, Aug 24, 2006 at 12:11:25PM -0700, Badari Pulavarty wrote:
> > Why can't you just use alloc_page? I bet the whole slab overhead
> > eats more memory than what's wasted when using alloc_pages. Especially
> > as the typical usecase is a 4k blocks filesystem with 4k pagesize
> > where the overhead of alloc_page is non-existant.
>
> Yes. That was what proposed earlier. But for 1k, 2k allocations we
> end up wasting whole page. Isn't it ? Thats why I created right
> sized slabs and disable slab-debug. I guess, I can do this only for
> 1k, 2k filesystems and directly use alloc_page() for 4k and 8k - but
> that would make code ugly and also it doesn't handle cases for
> bigger base pagesize systems (64k power).
Is there some way we can cleanly have a shortcut case where we use
alloc_page() if fs_blocksize == PAGE_SIZE? The efficiency gains for
what will be the common case on many architectures will probably make
this worthwhile....
- Ted
prev parent reply other threads:[~2006-08-25 2:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 23:08 [RFC][PATCH] Manage jbd allocations from its own slabs Badari Pulavarty
2006-08-23 23:34 ` Andrew Morton
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 ` 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=20060825022405.GA3692@thunk.org \
--to=tytso@mit.edu \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.