From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mx2.suse.de ([195.135.220.15]:40241 "EHLO mx1.suse.de"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1751667AbdJELGP (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
        Thu, 5 Oct 2017 07:06:15 -0400
Date: Thu, 5 Oct 2017 04:06:01 -0700
From: Davidlohr Bueso <dave@stgolabs.net>
To: Jan Kara <jack@suse.cz>
Cc: Waiman Long <longman@redhat.com>,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Jan Kara <jack@suse.com>,
        Jeff Layton <jlayton@poochiereds.net>,
        "J. Bruce Fields" <bfields@fieldses.org>,
        Tejun Heo <tj@kernel.org>,
        Christoph Lameter <cl@linux-foundation.org>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        Ingo Molnar <mingo@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Andi Kleen <andi@firstfloor.org>,
        Dave Chinner <dchinner@redhat.com>,
        Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH v6 5/6] lib/dlock-list: Enable faster lookup with hashing
Message-ID: <20171005110601.GA5131@linux-80c1.suse>
References: <1507152007-28753-1-git-send-email-longman@redhat.com>
 <1507152007-28753-6-git-send-email-longman@redhat.com>
 <20171005091406.GD28132@quack2.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20171005091406.GD28132@quack2.suse.cz>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Thu, 05 Oct 2017, Jan Kara wrote:

>OK, this makes sense but do you have any particular user in mind? In
>particular I'm not sure how big advantage this API brings over an existing
>one in include/linux/list_bl.h. Sure it's a tradeoff between bitlock /
>spinlock but is there a user where it matters?

This was tailored with epoll nested callbacks in mind, we've been discussing
offline. I have not looked at list_bl.h nonetheless.

Thanks,
Davidlohr