All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Waiman Long <longman@redhat.com>
Cc: 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 6/6] lib/dlock-list: Provide IRQ-safe APIs
Date: Wed, 4 Oct 2017 15:46:12 -0700	[thread overview]
Message-ID: <20171004224612.GF13815@linux-80c1.suse> (raw)
In-Reply-To: <1507152007-28753-7-git-send-email-longman@redhat.com>

On Wed, 04 Oct 2017, Waiman Long wrote:

>To enable the use of dlock-list in an interrupt handler, the following
>new APIs are provided for a irqsafe dlock-list:
>
> - void dlock_list_unlock_irqsafe(struct dlock_list_iter *)
> - void dlock_list_relock_irqsafe(struct dlock_list_iter *)
> - void dlock_list_add_irqsafe(struct dlock_list_node *,
>			       struct dlock_list_head *);
> - void dlock_lists_add_irqsafe(struct dlock_list_node *,
>				struct dlock_list_heads *)
> - void dlock_lists_del_irqsafe(struct dlock_list_node *)
>
>New macros for irqsafe dlock-list:
>
> - dlist_for_each_entry_irqsafe(pos, iter, member)
> - dlist_for_each_entry_safe_irqsafe(pos, n, iter, member)

Instead of adding more calls to the api, could we not just use the
irqsave/restore as part of the regular api?

Thanks,
Davidlohr

  reply	other threads:[~2017-10-04 22:46 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
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 [this message]
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=20171004224612.GF13815@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.