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
Date: Thu, 5 Oct 2017 04:06:01 -0700 [thread overview]
Message-ID: <20171005110601.GA5131@linux-80c1.suse> (raw)
In-Reply-To: <20171005091406.GD28132@quack2.suse.cz>
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
next prev parent reply other threads:[~2017-10-05 11:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 21:20 [PATCH v6 0/6] vfs: Use dlock list for SB's s_inodes list Waiman Long
2017-10-04 21:20 ` [PATCH v6 1/6] lib/dlock-list: Distributed and lock-protected lists Waiman Long
2017-10-04 21:20 ` [PATCH v6 2/6] vfs: Remove unnecessary list_for_each_entry_safe() variants Waiman Long
2017-10-04 21:20 ` [PATCH v6 3/6] vfs: Use dlock list for superblock's inode list Waiman Long
2017-10-04 21:20 ` [PATCH v6 4/6] lib/dlock-list: Make sibling CPUs share the same linked list Waiman Long
2017-10-05 8:59 ` Jan Kara
2017-10-05 14:57 ` Waiman Long
2017-10-09 7:26 ` Jan Kara
2017-10-05 17:40 ` Davidlohr Bueso
2017-10-05 18:01 ` Waiman Long
2017-10-07 13:44 ` kbuild test robot
2017-10-07 14:38 ` kbuild test robot
2017-10-04 21:20 ` [PATCH v6 5/6] lib/dlock-list: Enable faster lookup with hashing Waiman Long
2017-10-05 9:14 ` Jan Kara
2017-10-05 11:06 ` Davidlohr Bueso [this message]
2017-10-04 21:20 ` [PATCH v6 6/6] lib/dlock-list: Provide IRQ-safe APIs Waiman Long
2017-10-04 22:46 ` Davidlohr Bueso
2017-10-05 13:40 ` Waiman Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171005110601.GA5131@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=andi@firstfloor.org \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=cl@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox