On Wed, 21 Sep 2005, Jay Lan wrote: > I think the best approach would be to wrap the mm usage accounting > in a new CONFIG_ENHANCED_SYS_ACCT and leave it OFF by default so that > people can still get the minimal accounting with > CONFIG_BSD_PROCESS_ACCT. Sounds okay. - 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 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- From: Frank van Maarseveen <[email protected]>
- Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- From: Hugh Dickins <[email protected]>
- Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- From: Jay Lan <[email protected]>
- Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- From: Hugh Dickins <[email protected]>
- Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- From: Jay Lan <[email protected]>
- [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- Prev by Date: Re: [PATCH 2/2] suspend: Cleanup calling of power off methods.
- Next by Date: Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- Previous by thread: Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- Next by thread: Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
- Index(es):
