Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4758090pxj; Tue, 25 May 2021 16:03:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzb8wed2DtWtIh/O283aexF04Apn87uvixpqlO2zKwb+XvfGanz9eBc8a4QN0Fcb15RS8Qv X-Received: by 2002:a6b:d80b:: with SMTP id y11mr20258896iob.202.1621983811983; Tue, 25 May 2021 16:03:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621983811; cv=none; d=google.com; s=arc-20160816; b=bW/PomSjUfzbG+b9jO16H8EPMiI3KU47/+KtgCBDTA9bsMGQIm85ibU22PObu67efW ftcCONy9YPpEOCUToKzE57q+eBGs59wBNsria4Cv2cuDD84geJ0JB5n1zQVrVKnaKYSU GRLEd4D7nj5wX51yADunoXcPbbDCwu2hgsVl8f5b7gouxhvf/vV6LYRGK0R2wQEHqBYn KczhOaqcf6p8iU33c1NKG4KvnPJiW7y3DMr1o7kniyegvBWXqTqTv26KwxQ6GBu3meU9 Wd7RUxJOYAgtkAzIf7TURC+28LHwgeJyWDKZeuxx8P1t6LEm8fwOGTb2HDIKIdokU14U ge9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=t2QUVz6gnfCaqisemCBpqjC6VD3ID8/L7m//tDjqPVA=; b=0JIsIuXybH3B0YZq/GZlp9L7bDdM5yO52uEnyBHaU16y/Z44DErn3o7Svz86i/zTxN jXh86h8gWbGWqW3ayvRcYjpBuYu4I4LQzl/fN3+4YgAIjRdgSat5QKQFoRPokAhuQoWq /PtNDyuLbkxoSgaO1MODla4qrEPWpywJ9CtU6xPg4MXPnt6fGNWoFBvXm+cX4Bjz8VyF tw1YGHNisCMdYV+eNrRAN5yJn5ZjejoJ0UdetqfLIDcfxjxiY1VN5ltamX3BvBz8xAxO nwKKA0ru7nK2lDhVFc+jOA+2XMutuTagGuI9ZCDy8Ly5/4iBKjONjRl9oG1h2ZyCZ4lG iiAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gJQ+r3BB; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l15si6908428ilk.32.2021.05.25.16.03.19; Tue, 25 May 2021 16:03:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gJQ+r3BB; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231504AbhEYWdc (ORCPT + 99 others); Tue, 25 May 2021 18:33:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:43026 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231289AbhEYWdc (ORCPT ); Tue, 25 May 2021 18:33:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621981921; h=from:from:reply-to:subject:subject: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=t2QUVz6gnfCaqisemCBpqjC6VD3ID8/L7m//tDjqPVA=; b=gJQ+r3BBK1CPH+WTQ+Qk0d986+lmxiFqLVuskbFX7hICjp99LNViKrkpV1x1+V0bcPaAf/ AVQKL32iQc3eTdzBLZoTnC879x5dhOAZ1ESVz3TgOpabk7N+knqJQObpLaVpiU3/GuBZ2+ UYCFn2qASMSm9IVvTr45kyJ0/2kgSzE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-584-PqGiBbc9PpOTULD7UQr0ZQ-1; Tue, 25 May 2021 18:31:57 -0400 X-MC-Unique: PqGiBbc9PpOTULD7UQr0ZQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4E5FF107ACC7; Tue, 25 May 2021 22:31:56 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-112-24.rdu2.redhat.com [10.10.112.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id 794046062F; Tue, 25 May 2021 22:31:51 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <6E4DE257-4220-4B5B-B3D0-B67C7BC69BB5@dilger.ca> References: <6E4DE257-4220-4B5B-B3D0-B67C7BC69BB5@dilger.ca> <206078.1621264018@warthog.procyon.org.uk> To: Andreas Dilger Cc: dhowells@redhat.com, Theodore Ts'o , "Darrick J. Wong" , Chris Mason , Ext4 Developers List , xfs , linux-btrfs , linux-cachefs@redhat.com, linux-fsdevel , NeilBrown Subject: Re: How capacious and well-indexed are ext4, xfs and btrfs directories? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4169581.1621981910.1@warthog.procyon.org.uk> Date: Tue, 25 May 2021 23:31:50 +0100 Message-ID: <4169583.1621981910@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Andreas Dilger wrote: > As described elsewhere in the thread, allowing concurrent create and unlink > in a directory (rename probably not needed) would be invaluable for scaling > multi-threaded workloads. Neil Brown posted a prototype patch to add this > to the VFS for NFS: Actually, one thing I'm looking at is using vfs_tmpfile() to create a new file (or a replacement file when invalidation is required) and then using vfs_link() to attach directory entries in the background (possibly using vfs_link() with AT_LINK_REPLACE[1] instead of unlink+link). Any thoughts on how that might scale? vfs_tmpfile() doesn't appear to require the directory inode lock. I presume the directory is required for security purposes in addition to being a way to specify the target filesystem. David [1] https://lore.kernel.org/linux-fsdevel/cover.1580251857.git.osandov@fb.com/