From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Boaz Harrosh" <bharrosh@panasas.com>
Cc: "Hugh Dickins" <hugh@veritas.com>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
"Jens Axboe" <jens.axboe@oracle.com>,
"Christoph Lameter" <clameter@sgi.com>,
"Peter Zijlstra" <a.p.ziljstra@chello.nl>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
mpm@selenic.com, linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: scsi: fix sense_slab/bio swapping livelock
Date: Mon, 7 Apr 2008 13:17:54 +0300 [thread overview]
Message-ID: <84144f020804070317j4af69036q9801c288ba9ecac4@mail.gmail.com> (raw)
In-Reply-To: <47F9F266.4090107@panasas.com>
Hi Boaz,
On Mon, Apr 7, 2008 at 1:07 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
> Please forgive my ignorance, but what is then the difference between kmem_cache_alloc()
> and kmalloc?
Constructors, user-defined alignment, and tighter object packing.
On Mon, Apr 7, 2008 at 1:07 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
> would you not agree that sometimes we want to override that sharing of SLOBs?
To be honest, I really don't quite understand your use-case. But as
far as I can tell, it hasn't never been explicitly guaranteed and most
certainly has not been true since the merging of SLOB and more
recently SLUB.
Pekka
prev parent reply other threads:[~2008-04-07 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804062359.m36Nx3lA016774@hera.kernel.org>
[not found] ` <47F9EAD9.3060103@panasas.com>
[not found] ` <Pine.LNX.4.64.0804071248110.30814@sbz-30.cs.Helsinki.FI>
2008-04-07 10:07 ` Boaz Harrosh
2008-04-07 10:17 ` Pekka Enberg [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=84144f020804070317j4af69036q9801c288ba9ecac4@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=James.Bottomley@hansenpartnership.com \
--cc=a.p.ziljstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=clameter@sgi.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hugh@veritas.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®