From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3EB45C433F5 for ; Tue, 19 Apr 2022 12:50:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241635AbiDSMw7 (ORCPT ); Tue, 19 Apr 2022 08:52:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237698AbiDSMw6 (ORCPT ); Tue, 19 Apr 2022 08:52:58 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DD3C815813 for ; Tue, 19 Apr 2022 05:50:15 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 8AE501F74E; Tue, 19 Apr 2022 12:50:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1650372614; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0sKOzrWRyERklVfCfXwEn0UJv65Ihj5a5tXN8Iqupso=; b=0sFnP/nmZBxsj6hSoWTviC7xx6x7rqFWVs/9VEZOMqIivkeShZ2D3Kmm7nD7XpDgdstp8B slJW51dEDUtxzLdV2vQj9qU1cXfnfuvger75Tdi/DDdzzoNGWl336xSeI+obNHg02jY1Cu g7JGTHk+kzmS8UnykaPKoYvSg3GOd6Y= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1650372614; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0sKOzrWRyERklVfCfXwEn0UJv65Ihj5a5tXN8Iqupso=; b=3MvrLcpnylk3hDx8Ta1LL4NB9ZvJRFh6SsDu7eLDREtCN2fU13wqwxMPFjNKlM1eCR4v4T NQjduLC5arOmthCw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 720B3139BE; Tue, 19 Apr 2022 12:50:14 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id uVkPGwawXmJBdgAAMHmgww (envelope-from ); Tue, 19 Apr 2022 12:50:14 +0000 Date: Tue, 19 Apr 2022 14:46:11 +0200 From: David Sterba To: fdmanana@kernel.org Cc: linux-btrfs@vger.kernel.org Subject: Re: [PATCH 0/5] btrfs: avoid some block group rbtree lock contention Message-ID: <20220419124611.GA2348@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, fdmanana@kernel.org, linux-btrfs@vger.kernel.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Wed, Apr 13, 2022 at 04:20:38PM +0100, fdmanana@kernel.org wrote: > From: Filipe Manana > > This patchset allows for better concurrency when accessing the red black > tree of block groups, which is used very frequently and most accesses are > read-only, as well as avoid some unnecessary searches in the tree during > NOCOW writes. Details in the changelogs. > > Filipe Manana (5): > btrfs: remove search start argument from first_logical_byte() > btrfs: use rbtree with leftmost node cached for tracking lowest block group > btrfs: use a read/write lock for protecting the block groups tree > btrfs: return block group directly at btrfs_next_block_group() > btrfs: avoid double search for block group during NOCOW writes Added to misc-next, thanks.