On 08/05/2007 04:36 PM, Christoph Hellwig wrote: > > Umm, no f**king way. atime selection is 100% policy and belongs into > userspace. Add to that the problem that we can't actually re-enable > atimes because of the way the vfs-level mount flags API is designed. > Instead of doing such a fugly kernel patch just talk to the handfull > of distributions that matter to update their defaults. > We already tried that here. The response: "If noatime is so great, why isn't it the default in the kernel?" - 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 00/23] per device dirty throttling -v8
- From: Alan Cox <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Jeff Garzik <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- References:
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Jeff Garzik <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Jörn Engel <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Jörn Engel <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Jörn Engel <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- Prev by Date: Re: high system cpu load during intense disk i/o
- Next by Date: Re: [PATCH 00/10] foundations for reserve-based allocation
- Previous by thread: Re: [PATCH 00/23] per device dirty throttling -v8
- Next by thread: Re: [PATCH 00/23] per device dirty throttling -v8
- Index(es):