From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Date: Mon, 19 Sep 2016 09:28:59 +0200 Subject: [lustre-devel] [PATCH 030/124] staging: lustre: llite: Replace write mutex with range lock In-Reply-To: <1474231143-4061-31-git-send-email-jsimmons@infradead.org> References: <1474231143-4061-1-git-send-email-jsimmons@infradead.org> <1474231143-4061-31-git-send-email-jsimmons@infradead.org> Message-ID: <20160919072859.GA15407@kroah.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: James Simmons Cc: devel@driverdev.osuosl.org, Andreas Dilger , Oleg Drokin , Patrick Farrell , Linux Kernel Mailing List , Jinshan Xiong , Prakash Surya , Lustre Development List On Sun, Sep 18, 2016 at 04:37:29PM -0400, James Simmons wrote: > + * Range lock is used to allow multiple threads writing a single shared > + * file given each thread is writing to a non-overlapping portion of the > + * file. > + * > + * Refer to the possible upstream kernel version of range lock by > + * Jan Kara : https://lkml.org/lkml/2013/1/31/480 > + * > + * This file could later replaced by the upstream kernel version. It doesn't look like range_lock ever got accepted in the kernel tree, any idea what happened to it? Having a per-filesystem lock type seems odd to me... thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936497AbcISH3N (ORCPT ); Mon, 19 Sep 2016 03:29:13 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:32820 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935495AbcISH2z (ORCPT ); Mon, 19 Sep 2016 03:28:55 -0400 Date: Mon, 19 Sep 2016 09:28:59 +0200 From: Greg Kroah-Hartman To: James Simmons Cc: devel@driverdev.osuosl.org, Andreas Dilger , Oleg Drokin , Patrick Farrell , Linux Kernel Mailing List , Jinshan Xiong , Prakash Surya , Lustre Development List Subject: Re: [PATCH 030/124] staging: lustre: llite: Replace write mutex with range lock Message-ID: <20160919072859.GA15407@kroah.com> References: <1474231143-4061-1-git-send-email-jsimmons@infradead.org> <1474231143-4061-31-git-send-email-jsimmons@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1474231143-4061-31-git-send-email-jsimmons@infradead.org> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 18, 2016 at 04:37:29PM -0400, James Simmons wrote: > + * Range lock is used to allow multiple threads writing a single shared > + * file given each thread is writing to a non-overlapping portion of the > + * file. > + * > + * Refer to the possible upstream kernel version of range lock by > + * Jan Kara : https://lkml.org/lkml/2013/1/31/480 > + * > + * This file could later replaced by the upstream kernel version. It doesn't look like range_lock ever got accepted in the kernel tree, any idea what happened to it? Having a per-filesystem lock type seems odd to me... thanks, greg k-h