public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: kent.overstreet@gmail.com, shli@kernel.org
Cc: linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
	i@coly.li, nborisov@suse.com, linux-kernel@vger.kernel.org,
	kernel-team@lge.com
Subject: Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
Date: Fri, 18 Aug 2017 10:24:26 +0900	[thread overview]
Message-ID: <20170818012426.GX20323@X58A-UD3R> (raw)
In-Reply-To: <1502426543-15229-1-git-send-email-byungchul.park@lge.com>

On Fri, Aug 11, 2017 at 01:42:23PM +0900, Byungchul Park wrote:
> Although llist provides proper APIs, they are not used. Make them used.

Any opinions about this?

> 
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> Acked-by: Coly Li <colyli@suse.de>
> ---
>  drivers/md/bcache/closure.c | 15 ++-------------
>  1 file changed, 2 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c
> index 864e673..7d5286b 100644
> --- a/drivers/md/bcache/closure.c
> +++ b/drivers/md/bcache/closure.c
> @@ -70,21 +70,10 @@ void __closure_wake_up(struct closure_waitlist *wait_list)
>  	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(cl, reverse, list) {
>  		closure_set_waiting(cl, 0);
>  		closure_sub(cl, CLOSURE_WAITING + 1);
>  	}
> -- 
> 1.9.1

  reply	other threads:[~2017-08-18  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  4:42 [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API Byungchul Park
2017-08-18  1:24 ` Byungchul Park [this message]
2017-08-18  6:04   ` Coly Li
2017-08-18  6:10     ` Byungchul Park
2017-09-05  2:37     ` Byungchul Park
2017-09-05  2:54       ` Coly Li

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=20170818012426.GX20323@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=i@coly.li \
    --cc=kent.overstreet@gmail.com \
    --cc=kernel-team@lge.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=shli@kernel.org \
    /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