From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cn.fujitsu.com ([222.73.24.84]:20242 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750887Ab2JZBzo (ORCPT ); Thu, 25 Oct 2012 21:55:44 -0400 Message-ID: <5089EDB7.8030306@cn.fujitsu.com> Date: Fri, 26 Oct 2012 09:56:07 +0800 From: Miao Xie Reply-To: miaox@cn.fujitsu.com MIME-Version: 1.0 To: Liu Bo CC: Linux Btrfs Subject: Re: [PATCH 0/3] flush delalloc by multi-task References: <5089045D.8050801@cn.fujitsu.com> <50892821.5010808@oracle.com> In-Reply-To: <50892821.5010808@oracle.com> Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On thu, 25 Oct 2012 19:53:05 +0800, Liu Bo wrote: > On 10/25/2012 05:20 PM, Miao Xie wrote: >> This patchset introduce multi-task delalloc flush, it can make the delalloc >> flush more faster. And besides that, it also can fix the problem that we join >> the same transaction handler more than 2 times. >> >> Implementation: >> - Create a new worker pool. >> - Queue the inode with pending delalloc into the work queue of the worker pool >> when we want to force them into the disk, and then we will wait till all the >> works we submit are done. >> - The ordered extents also can be queued into this work queue. The process is >> similar to the second one. >> > > I can see the potential improvements brought by flushing inodes this way. > > But I don't think it makes much sense by making waiting process multi-task, > since even we spread wait order extents into different cpus, they just occpied > the cpu and went on waiting and scheduled then, I mean, the bottleneck is on > what we're waiting for. Thanks for your comment, I think only btrfs_run_ordered_operations(root, 0) needn't wait for the works, the others must wait. The first reason is to avoid changing the semantic of those tree function. The second reason is we have to wait for the completion of all works, if not, the file data in snapshots may be different with the source suvolumes because the flush may not end before the snapshot creation. > Besides, considering that this patchset is about to getting us better performance, > I'm expecting any performance numbers (I'm a little worried about context switches > overhead). OK, I'll send it out later. Thanks Miao > btw, cool ideas indeed. > > thanks, > liubo > >> Miao Xie (3): >> Btrfs: make delalloc inodes be flushed by multi-task >> Btrfs: make ordered operations be handled by multi-task >> Btrfs: make ordered extent be flushed by multi-task >> >> fs/btrfs/ctree.h | 14 +++++++ >> fs/btrfs/disk-io.c | 7 ++++ >> fs/btrfs/inode.c | 78 ++++++++++++++++++++++++++++++++++++++--- >> fs/btrfs/ordered-data.c | 87 ++++++++++++++++++++++++++++++++++------------- >> fs/btrfs/ordered-data.h | 7 +++- >> fs/btrfs/relocation.c | 6 +++- >> fs/btrfs/transaction.c | 24 ++++++++++--- >> 7 files changed, 185 insertions(+), 38 deletions(-) >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >