Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes

 
> Well, it creates arch-neutral common code, teaches various architectures
> use it.  It's the sort of thing we do all the time.
> 
> These things are opportunities to eliminate crufty arch code which few
> people understand and replace them with new, clean common code which lots
> of people understand.  That's not a bad thing to be doing.

I'm not fundamentally against that, but so far it seems to just generate lots of 
new bugs?  I'm not sure it's really worth the pain.

-Andi
-
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 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
  - From: Andrew Morton <[email protected]>

References:
- [PATCH 0/6] Sizing zones and holes in an architecture independent manner V6
  - From: Mel Gorman <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
  - From: Andi Kleen <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: [git patches] net driver updates
Next by Date: Re: pktcdvd major contradicts <linux/Documentation/devices.txt>
Previous by thread: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
Next by thread: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
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]