On 6/4/07, Christoph Lameter <[email protected]> wrote:
We are doing that right now. The problem is that people keep storing stuff in memory allocated with kmalloc(0).
Ok, makes sense. I guess I might as well throw my suggestion in the mix. Lets create a new kmalloc cache for zero-length objects where object size is zero but there are regular red-zones on both sides. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Linus Torvalds <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- References:
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Andrew Morton <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Andrew Morton <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: "Pekka Enberg" <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Prev by Date: Re: thinkpad testers wanted (was Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?)
- Next by Date: Re: b44: regression in 2.6.22 (resend)
- Previous by thread: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Next by thread: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Index(es):