linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, cmm@us.ibm.com,
	ext2-devel@lists.sourceforge.net,
	Badari Pulavarty <pbadari@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem
Date: Thu, 10 Aug 2006 12:54:29 -0700	[thread overview]
Message-ID: <20060810125429.6dded9b6.akpm@osdl.org> (raw)
In-Reply-To: <1155238570.12082.11.camel@kleikamp.austin.ibm.com>

On Thu, 10 Aug 2006 14:36:10 -0500
Dave Kleikamp <shaggy@austin.ibm.com> wrote:

> On Thu, 2006-08-10 at 12:23 -0700, Andrew Morton wrote:
> > On Thu, 10 Aug 2006 11:51:34 -0700
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > 
> > > Andrew Morton wrote:
> > > > Also, JBD is presently feeding into submit_bh() buffer_heads which span two
> > > > machine pages, and some device drivers spit the dummy.  It'd be better to
> > > > fix that once, rather than twice..  
> > > >   
> > > Andrew,
> > > 
> > > I looked at this few days ago. I am not sure how we end up having 
> > > multiple pages (especially,
> > > why we end up having buffers with bh_size > pagesize) ? Do you know why ?
> > > 
> > 
> > It's one or both of the jbd_kmalloc(bh->b_size) calls in
> > fs/jbd/transaction.c.  Here we're allocating data to attach to a bh which
> > later gets fed into submit_bh().
> > 
> > Problem is, with CONFIG_DEBUG_SLAB=y, the data which kmalloc() returns can
> > be offset by 4 bytes due to redzoning.
> > 
> > Example: if the fs is using a 1k blocksize and we have a 4k pagesize, the
> > data coming back from kmalloc may have an address of 0xnnnnxc04, so the
> > data which we later feed into submit_bh() will span two pages.
> > 
> > A simple fix would be to replace kmalloc() with a call to alloc_page(). 
> > We'd need to work out how much memory that will worst-case-waste.  If "not
> > much" then OK.
> > 
> > If "quite a lot in the worst case" then we'd need something more elaborate.
> 
> Would some like this be okay:
> 
> #ifdef CONFIG_DEBUG_SLAB
> 	return alloc_page(...
> #else
> 	return kmalloc(...
> #endif
> 
> This keeps it simple, and should be still be efficient in the
> non-DEBUG_SLAB case.
> 

I guess that would work OK.  It does appear that a lot of people build and
distribute CONFIG_DEBUG_SLAB kernels though.  Fedora, for one.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-08-10 19:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:17 [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem Mingming Cao
2006-08-10  6:39 ` Andrew Morton
2006-08-10 16:41   ` Mingming Cao
2006-08-10 16:48     ` Jörn Engel
2006-08-10 18:18     ` Andrew Morton
2006-08-10 20:22       ` Jeff Garzik
2006-08-10 20:33         ` Andrew Morton
2006-08-10 20:52           ` Jeff Garzik
2006-08-10 17:44   ` Theodore Tso
2006-08-10 18:51   ` Badari Pulavarty
2006-08-10 19:23     ` Andrew Morton
2006-08-10 19:36       ` Dave Kleikamp
2006-08-10 19:54         ` Andrew Morton [this message]
2006-08-10 20:12       ` Jeff Garzik
2006-08-10 20:13     ` Jeff Garzik
2006-08-10 20:27       ` Andrew Morton
2006-08-10 21:00         ` Jeff Garzik
2006-08-10 21:11           ` Alex Tomas
2006-08-10 22:18             ` [Ext2-devel] " 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=20060810125429.6dded9b6.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=shaggy@austin.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;
as well as URLs for NNTP newsgroup(s).