Re: [PATCH] Fix kernel BUGs when enable SLOB allocator

Hi Nick,

We are using SLOB allocator, why need to set PageSlab?
If later there come forth another type of allocator(SLEB, SLUB), Do we
still need to set PageSlab bit?

On the other hand, I'm not sure if the current SLOB code works
properly on the MMU system. If so, I think changing the nommu.c should
be a better solution.

Regards,
-Aubrey

On 6/27/06, Nick Piggin <[email protected]> wrote:

Then what if objp isn't a slob object?

I think the better fix would be to make slob set PageSlab.

--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com

-
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/

---

• References:
  • [PATCH] Fix kernel BUGs when enable SLOB allocator
    • From: Aubrey <[email protected]>
  • Re: [PATCH] Fix kernel BUGs when enable SLOB allocator
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [PATCH 1/2] srcu: RCU variant permitting read-side blocking
• Next by Date: Re: [PATCH] get USB suspend to work again on 2.6.17-mm1
• Previous by thread: Re: [PATCH] Fix kernel BUGs when enable SLOB allocator
• Next by thread: [PATCH] Clean up the bootmem allocator
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]