public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: peterz@infradead.org, mingo@kernel.org, neilb@suse.de,
	nab@linux-iscsi.org, viro@zeniv.linux.org.uk
Cc: ying.huang@intel.com, oleg@redhat.com, shli@kernel.org,
	linux-kernel@vger.kernel.org, koverstreet@google.com,
	kernel-team@lge.com, jkosina@suse.cz
Subject: Re: [PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API
Date: Fri, 3 Mar 2017 08:16:29 +0900	[thread overview]
Message-ID: <20170302231629.GC28562@X58A-UD3R> (raw)
In-Reply-To: <1487057190-25191-3-git-send-email-byungchul.park@lge.com>

On Tue, Feb 14, 2017 at 04:26:23PM +0900, Byungchul Park wrote:
> Although llist provides proper APIs, they are not used. Make them used.

+ koverstreet@google.com
+ jkosina@suse.cz

I am not sure who I should cc for this subsystem..
Could you check this patch?

Thanks,
Byungchul

> 
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
>  drivers/md/bcache/closure.c | 17 +++--------------
>  1 file changed, 3 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c
> index 864e673..1841d03 100644
> --- a/drivers/md/bcache/closure.c
> +++ b/drivers/md/bcache/closure.c
> @@ -64,27 +64,16 @@ void closure_put(struct closure *cl)
>  void __closure_wake_up(struct closure_waitlist *wait_list)
>  {
>  	struct llist_node *list;
> -	struct closure *cl;
> +	struct closure *cl, *t;
>  	struct llist_node *reverse = NULL;
>  
>  	list = llist_del_all(&wait_list->list);
>  
>  	/* We first reverse the list to preserve FIFO ordering and fairness */
> -
> -	while (list) {
> -		struct llist_node *t = list;
> -		list = llist_next(list);
> -
> -		t->next = reverse;
> -		reverse = t;
> -	}
> +	reverse = llist_reverse_order(list);
>  
>  	/* Then do the wakeups */
> -
> -	while (reverse) {
> -		cl = container_of(reverse, struct closure, list);
> -		reverse = llist_next(reverse);
> -
> +	llist_for_each_entry_safe(cl, t, reverse, list) {
>  		closure_set_waiting(cl, 0);
>  		closure_sub(cl, CLOSURE_WAITING + 1);
>  	}
> -- 
> 1.9.1

  reply	other threads:[~2017-03-02 23:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14  7:26 [PATCH v3 0/9] Don't reinvent the wheel but use existing llist API Byungchul Park
2017-02-14  7:26 ` [PATCH v3 1/9] llist: Provide a safe version for llist_for_each Byungchul Park
2017-02-14  7:45   ` Huang, Ying
2017-03-02 22:59     ` Byungchul Park
2017-03-21  2:53     ` Byungchul Park
2017-02-14  7:26 ` [PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API Byungchul Park
2017-03-02 23:16   ` Byungchul Park [this message]
2017-03-05 19:59     ` Jiri Kosina
2017-03-05 22:51       ` Byungchul Park
2017-03-05 22:54   ` Byungchul Park
2017-03-24  0:27   ` Byungchul Park
2017-02-14  7:26 ` [PATCH v3 3/9] raid5: " Byungchul Park
2017-02-16 22:48   ` Shaohua Li
2017-02-14  7:26 ` [PATCH v3 4/9] vhost/scsi: " Byungchul Park
2017-02-19  5:42   ` Nicholas A. Bellinger
2017-02-14  7:26 ` [PATCH v3 5/9] fput: " Byungchul Park
2017-02-14 17:44   ` Oleg Nesterov
2017-03-02 23:09     ` Byungchul Park
2017-02-14  7:26 ` [PATCH v3 6/9] namespace.c: " Byungchul Park
2017-02-14  7:26 ` [PATCH v3 7/9] irq_work: " Byungchul Park
2017-02-14  7:26 ` [PATCH v3 8/9] sched: " Byungchul Park
2017-02-22  5:04   ` Byungchul Park
2017-02-14  7:26 ` [PATCH v3 9/9] mm: " Byungchul Park
2017-05-02  8:03 ` [PATCH v3 0/9] " Byungchul Park

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=20170302231629.GC28562@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=jkosina@suse.cz \
    --cc=kernel-team@lge.com \
    --cc=koverstreet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=neilb@suse.de \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shli@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ying.huang@intel.com \
    /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