linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Andreas Dilger <adilger@sun.com>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	penberg@cs.helsinki.fi, arjan@infradead.org,
	linux-kernel@vger.kernel.org, cl@linux-foundation.org,
	npiggin@suse.de, linux-ext4@vger.kernel.org
Subject: Re: upcoming kerneloops.org item: get_page_from_freelist
Date: Thu, 25 Jun 2009 18:05:04 -0400	[thread overview]
Message-ID: <20090625220504.GG6472@mit.edu> (raw)
In-Reply-To: <20090625212628.GO3385@webber.adilger.int>

On Thu, Jun 25, 2009 at 11:26:28PM +0200, Andreas Dilger wrote:
> IIRC there was also a good reason for this in the past, related to
> the buffers being submitted to the block device layer, and if they
> were allocated from the slab cache with CONFIG_DEBUG_SLAB or something
> similar enabled the buffer would be misaligned and cause grief.

So what does SLAB/SLUB/SLOB do if we create a slab cache which is a
power of two?  Can one of the allocators still return misaligned
blocks of memory in some circumstances?

						- Ted

  reply	other threads:[~2009-06-25 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.01.0906241240360.3154@localhost.localdomain>
     [not found] ` <20090624130121.99321cca.akpm@linux-foundation.org>
     [not found]   ` <alpine.LFD.2.01.0906241312090.3154@localhost.localdomain>
     [not found]     ` <alpine.LFD.2.01.0906241334260.3154@localhost.localdomain>
     [not found]       ` <20090624150714.c7264768.akpm@linux-foundation.org>
     [not found]         ` <20090625132544.GB9995@mit.edu>
     [not found]           ` <alpine.DEB.2.00.0906251135440.30090@chino.kir.corp.google.com>
     [not found]             ` <20090625193806.GA6472@mit.edu>
     [not found]               ` <20090625194423.GB6472@mit.edu>
     [not found]                 ` <alpine.DEB.2.00.0906251257040.3086@chino.kir.corp.google.com>
2009-06-25 20:37                   ` upcoming kerneloops.org item: get_page_from_freelist Theodore Tso
2009-06-25 21:05                     ` Joel Becker
2009-06-25 21:26                     ` Andreas Dilger
2009-06-25 22:05                       ` Theodore Tso [this message]
2009-06-25 22:11                         ` Eric Sandeen
2009-06-26  1:11                           ` Theodore Tso
2009-06-26  5:16                             ` Pekka J Enberg
2009-06-26  8:56                               ` Nick Piggin
2009-06-26  8:58                                 ` Pekka Enberg
2009-06-26  9:07                                   ` Nick Piggin
2009-06-29 21:06                                   ` Christoph Lameter
2009-06-30  7:59                                     ` Nick Piggin
2009-06-26 14:41                               ` Eric Sandeen
2009-06-29 21:15                                 ` Christoph Lameter
2009-06-29 21:20                                   ` Eric Sandeen
2009-06-29 22:35                                     ` Christoph Lameter

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=20090625220504.GG6472@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.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).