On Tue, 30 May 2006, Hugh Dickins wrote: > Your original question, whether they could be combined, was a good one; > and I hoped you'd be right. But I agree with David, they cannot, unless > we sacrifice the guarantee that one or the other is there to give. It's > much like the relationship between ->prepare_write and ->commit_write. Ok, so separate patch sets? - 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 1/3] mm: tracking shared dirty pages
- From: Hugh Dickins <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- References:
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: Christoph Lameter <[email protected]>
- [PATCH 0/3] mm: tracking dirty pages -v5
- From: Peter Zijlstra <[email protected]>
- [PATCH 1/3] mm: tracking shared dirty pages
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: David Howells <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: David Howells <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: David Howells <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- From: Hugh Dickins <[email protected]>
- Re: [PATCH 1/3] mm: tracking shared dirty pages
- Prev by Date: Re: [PATCH 1/3] mm: tracking shared dirty pages
- Next by Date: Re: [patch 05/61] lock validator: introduce WARN_ON_ONCE(cond)
- Previous by thread: Re: [PATCH 1/3] mm: tracking shared dirty pages
- Next by thread: Re: [PATCH 1/3] mm: tracking shared dirty pages
- Index(es):