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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0414DC43387 for ; Thu, 10 Jan 2019 08:38:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BC673206B6 for ; Thu, 10 Jan 2019 08:38:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=szeredi.hu header.i=@szeredi.hu header.b="fuhcyaY4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727502AbfAJIiO (ORCPT ); Thu, 10 Jan 2019 03:38:14 -0500 Received: from mail-io1-f65.google.com ([209.85.166.65]:36002 "EHLO mail-io1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727342AbfAJIiO (ORCPT ); Thu, 10 Jan 2019 03:38:14 -0500 Received: by mail-io1-f65.google.com with SMTP id m19so8298386ioh.3 for ; Thu, 10 Jan 2019 00:38:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QtKQjT/UJnCuD8vHY3T9VcFlAltO26LqWHtYUyLbzds=; b=fuhcyaY4WIMgh6NOx12IMWWE5P7T7iCylKtr0AgS3975LC8DC0gFENlvX0mEo3rDjM qCu7JFE7f022gDM1mAZPinsEXSh6t3O+9e3C+RongcS3isq/L1GIP2NJP1yMVAQwg1TR ifyFLDDAtFlPWhDM1iIoWdmtCFUMrW24QVp6g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QtKQjT/UJnCuD8vHY3T9VcFlAltO26LqWHtYUyLbzds=; b=sD4FcCyYVCFzBswMKqoJfrgNVTz2iUezuPQpHFqUhTS+EIKm7agVsb66tx80cZUG7J 4ktF0Pk6ys34RFTlkmlLs7FxYGrfqLC1missu2+uu9i1Uw5PsFNdMD0aDH1T6fq/NxrN D5egq35T/eNSmsvzM17YR+8u3XrWDV6XVijZHfT2O+9bLbNAYgpXxHz5ntYyXCuAucpi 7GjDQ1RFI/wZpjisnqGoYW1MsV+S7vuVgmOvnW+k+Egwq4KpwmVmlxHyJ7g9F87nWL6Z 74O89t7rmzog4h4dGqe7LYrZi6xm8P1LvIPkfCh4gNhdXtool39J7D6A6eUZ+4MuZYZZ HXAA== X-Gm-Message-State: AJcUukcrHej744ad/ggEM3p41jznXEeEdeffnr/YYVBDXNgNtPtDEPKF zm2G4qJp8/WVx/nyTAlWynaMZnkEYskanYL2s9Ku7A== X-Google-Smtp-Source: ALg8bN7rULEy4oij9XHaRdkTqkX1ZqNKIO1C/OW+OBNDWrOUMq9qoiL5XNkPs+79McRHDle7VnxWoAj51Tnf6+CL5dw= X-Received: by 2002:a5e:da49:: with SMTP id o9mr5924785iop.246.1547109493206; Thu, 10 Jan 2019 00:38:13 -0800 (PST) MIME-Version: 1.0 References: <154175935554.21228.11270624605198037428.stgit@localhost.localdomain> In-Reply-To: From: Miklos Szeredi Date: Thu, 10 Jan 2019 09:38:02 +0100 Message-ID: Subject: Re: [PATCH v2 0/5] fuse: Further reducing contention of fc->lock To: Kirill Tkhai Cc: linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, Dec 10, 2018 at 5:20 PM Kirill Tkhai wrote: > > ping > > On 09.11.2018 13:33, Kirill Tkhai wrote: > > v2: Removed patch [1/6] from v1, and [4/6] from v1 is replaced > > with new patch (which is [2/5] in this v2). > > > > There was introduced fc->bg_lock to reduce the contention, > > and this patchset continues this efforts. > > > > This patchset introduces per fuse_inode lock to protect > > inode metadata, synchronization with background writes, etc. > > All of the above is related to a single inode, and there > > is no a reason, that inodes are concurrents of each other > > to make some of actions exclusive. > > > > So, here we introduce fuse_inode::lock spinlock and get rid > > of fc->lock in many places. Pushed to fuse.git#for-next. Thanks, Miklos