From: Chris Mason <chris.mason@oracle.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
cmm@us.ibm.com, jack@suse.cz, linux-ext4@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext2: Use page_mkwrite vma_operations to get mmap write notification.
Date: Thu, 12 Jun 2008 08:22:43 -0400 [thread overview]
Message-ID: <1213273364.10187.281.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20080612040643.GA5518@skywalker>
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@linux.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
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
cmm@us.ibm.com, jack@suse.cz, linux-ext4@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext2: Use page_mkwrite vma_operations to get mmap write notification.
Date: Thu, 12 Jun 2008 08:22:43 -0400 [thread overview]
Message-ID: <1213273364.10187.281.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20080612040643.GA5518@skywalker>
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@linux.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-06-12 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 17:05 [PATCH] ext2: Use page_mkwrite vma_operations to get mmap write notification Aneesh Kumar K.V
2008-06-05 17:05 ` [PATCH] ext3: " Aneesh Kumar K.V
2008-06-05 19:30 ` [PATCH] ext2: " Andrew Morton
2008-06-05 19:30 ` Andrew Morton
2008-06-11 15:08 ` Aneesh Kumar K.V
2008-06-11 15:08 ` Aneesh Kumar K.V
2008-06-11 19:07 ` Andrew Morton
2008-06-11 19:07 ` Andrew Morton
2008-06-12 4:06 ` Aneesh Kumar K.V
2008-06-12 4:06 ` Aneesh Kumar K.V
2008-06-12 12:22 ` Chris Mason [this message]
2008-06-12 12:22 ` Chris Mason
2008-06-12 16:17 ` Jan Kara
2008-06-12 16:17 ` Jan Kara
2008-06-22 22:50 ` Dave Chinner
2008-06-22 22:50 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 18:24 Patches for the patchqueue Aneesh Kumar K.V
2008-06-06 18:24 ` [PATCH] ext4: cleanup blockallocator Aneesh Kumar K.V
2008-06-06 18:24 ` [PATCH] ext2: Use page_mkwrite vma_operations to get mmap write notification Aneesh Kumar K.V
2008-03-24 17:04 [PATCH] ext3: Return EIO if new block is allocated from system zone Aneesh Kumar K.V
2008-03-24 17:04 ` [PATCH] ext3: Use page_mkwrite vma_operations to get mmap write notification Aneesh Kumar K.V
2008-03-24 17:04 ` [PATCH] ext4: Export needed symbol for ZERO_PAGE usage in modules Aneesh Kumar K.V
2008-03-24 17:04 ` [PATCH] ext2: Use page_mkwrite vma_operations to get mmap write notification Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213273364.10187.281.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.