Re: [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)

Dave Hansen writes:

> Why am I doing this?  The OpenVZ beancounter patch hooks into the
> alloc_thread_info() path, but only in two architectures.  It is silly
> to patch each and every architecture when they all just do the same
> thing.  This is the first step to have a single place in which to
> do alloc_thread_info().  Oh, and this series removes about 300 lines
> of code.

... at the price of making the Kconfig help text more generic and
therefore possibly confusing on some platforms.

I really don't see much value in doing all this.

Paul.
-
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: [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)
    • From: Dave Hansen <[email protected]>

• References:
  • [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)
    • From: Dave Hansen <[email protected]>

• Prev by Date: [PATCH 7/8] Implement smp_processor_id() with the PDA.
• Next by Date: [PATCH 1/8] Use asm-offsets for the offsets of registers into the pt_regs struct, rather than having hard-coded constants.
• Previous by thread: [RFC][PATCH 6/9] mips generic PAGE_SIZE
• Next by thread: Re: [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4)
• 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]