Re: [PATCH 1/2] Account for module percpu space separately from kernel percpu

Jeremy Fitzhardinge <[email protected]> writes:

> Rather than using a single constant PERCPU_ENOUGH_ROOM, compute it as
> the sum of kernel_percpu + PERCPU_MODULE_RESERVE.  This is now common
> to all architectures; if an architecture wants to set
> PERCPU_ENOUGH_ROOM to something special, then it may do so (ia64 is
> the only one which does).

I think I have already done this but in case I haven't.
Acked-by: "Eric W. Biederman" <[email protected]>

I see any problems there.
-
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: [PATCH 1/2] Account for module percpu space separately from kernel percpu
    • From: Jeremy Fitzhardinge <[email protected]>

• References:
  • [PATCH 1/2] Account for module percpu space separately from kernel percpu
    • From: Jeremy Fitzhardinge <[email protected]>

• Prev by Date: Re: [PATCH 9/10] Vmi timer update.patch
• Next by Date: Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
• Previous by thread: [PATCH 1/2] Account for module percpu space separately from kernel percpu
• Next by thread: Re: [PATCH 1/2] Account for module percpu space separately from kernel percpu
• 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]