[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706081536560.3966@schroedinger.engr.sgi.com>
Date: Fri, 8 Jun 2007 15:38:02 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: "Siddha, Suresh B" <suresh.b.siddha@...el.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
Andreas Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
gregkh@...e.de, muli@...ibm.com, asit.k.mallick@...el.com,
arjan@...ux.intel.com, ashok.raj@...el.com, shaohua.li@...el.com,
davem@...emloft.net
Subject: Re: [Intel-IOMMU 02/10] Library routine for pre-allocat pool handling
On Fri, 8 Jun 2007, Siddha, Suresh B wrote:
> > If for some reason you really can't do that (and a requirement for
> > allocation-in-interrupt is the only valid reason, really) and if you indeed
> > can demonstrate memory allocation failures with certain workloads then
> > let's take a look at that. As I said, attaching a reserve pool to your
> > slab cache might be a suitable approach. But none of these things are
>
> I agree. We are better off with enhancing slab infrastructure for this, if
> needed.
The slab allocators already use the page allocators atomic reserves if
called with GFP_ATOMIC.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists