[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1213273364.10187.281.camel@think.oraclecorp.com>
Date: Thu, 12 Jun 2008 08:22:43 -0400
From: Chris Mason <chris.mason@...cle.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, cmm@...ibm.com,
jack@...e.cz, linux-ext4@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext2: Use page_mkwrite vma_operations to get mmap
write notification.
On Thu, 2008-06-12 at 09:36 +0530, Aneesh Kumar K.V wrote:
> On Wed, Jun 11, 2008 at 12:07:49PM -0700, Andrew Morton wrote:
> > On Wed, 11 Jun 2008 20:38:45 +0530
> > "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> wrote:
> The idea is to have ext3/4_writepages. In writepages start a transaction
> and iterate over the pages take the lock and do block allocation. With
> that change we should be able to not do block allocation in the
> page_mkwrite path. We may still want to do block reservation there.
>
> Something like.
>
> ext4_writepages()
> {
> journal_start()
> for_each_page()
Even with delayed allocation, the vast majority of the pages won't need
any allocations. You'll hit delalloc, do a big chunk with the journal
lock held and then do simple writepages that don't need anything
special.
I know the jbd journal_start is cheaper than the reiserfs one is, but it
might not perform well to hold it across the long writepages loop. At
least reiser saw a good boost when I stopped calling journal_begin in
writepage unless the page really needed allocations.
With the loop you have in mind, it is easy enough to back out and start
the transaction only when required.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists