Hi! > So far all first-hand experiences I heard of were positive (i.e. I did > not get an emaail from anyone saying: It had a negative effect for me), > so I propose to apply the patch from Con Kolivas. The wording in the > description still very strongly recommends to not change that value, and > it's still dependent on EXPERIMENTAL. I append the patch just because There's a big difference between 'experimental' and 'known to broke obscure userspace apps'. -- Thanks for all the (sleeping) penguins. - 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: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Norbert Kiesel <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- References:
- Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Norbert Kiesel <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Arjan van de Ven <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Norbert Kiesel <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Adrian Bunk <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Alejandro Riveira Fernández <[email protected]>
- Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- From: Norbert Kiesel <[email protected]>
- Why is "Memory split" Kconfig option only for EMBEDDED?
- Prev by Date: Re: 2.6.19, more unwinder problems ...
- Next by Date: Re: [PATCH] Introduce time_data, a new structure to hold jiffies, xtime, xtime_lock, wall_to_monotonic, calc_load_count and avenrun
- Previous by thread: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- Next by thread: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
- Index(es):
 |