From: Jan Kara <jack@suse.cz>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 2/3] block: Stop abusing rq->csd.list in blk-softirq
Date: Wed, 18 Dec 2013 21:50:58 +0100 [thread overview]
Message-ID: <20131218205058.GC13685@quack.suse.cz> (raw)
In-Reply-To: <1387387418-10005-5-git-send-email-jack@suse.cz>
On Wed 18-12-13 18:23:36, Jan Kara wrote:
> Abusing rq->csd.list for a list of requests to complete is rather ugly.
> Especially since using queuelist should be safe and much cleaner.
This is the correct patch 2/3.
Honza
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> block/blk-softirq.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/block/blk-softirq.c b/block/blk-softirq.c
> index 57790c1a97eb..7ea5534096d5 100644
> --- a/block/blk-softirq.c
> +++ b/block/blk-softirq.c
> @@ -30,8 +30,8 @@ static void blk_done_softirq(struct softirq_action *h)
> while (!list_empty(&local_list)) {
> struct request *rq;
>
> - rq = list_entry(local_list.next, struct request, csd.list);
> - list_del_init(&rq->csd.list);
> + rq = list_entry(local_list.next, struct request, queuelist);
> + list_del_init(&rq->queuelist);
> rq->q->softirq_done_fn(rq);
> }
> }
> @@ -45,9 +45,9 @@ static void trigger_softirq(void *data)
>
> local_irq_save(flags);
> list = this_cpu_ptr(&blk_cpu_done);
> - list_add_tail(&rq->csd.list, list);
> + list_add_tail(&rq->queuelist, list);
>
> - if (list->next == &rq->csd.list)
> + if (list->next == &rq->queuelist)
> raise_softirq_irqoff(BLOCK_SOFTIRQ);
>
> local_irq_restore(flags);
> @@ -136,7 +136,7 @@ void __blk_complete_request(struct request *req)
> struct list_head *list;
> do_local:
> list = this_cpu_ptr(&blk_cpu_done);
> - list_add_tail(&req->csd.list, list);
> + list_add_tail(&req->queuelist, list);
>
> /*
> * if the list only contains our just added request,
> @@ -144,7 +144,7 @@ do_local:
> * entries there, someone already raised the irq but it
> * hasn't run yet.
> */
> - if (list->next == &req->csd.list)
> + if (list->next == &req->queuelist)
> raise_softirq_irqoff(BLOCK_SOFTIRQ);
> } else if (raise_blk_irq(ccpu, req))
> goto do_local;
> --
> 1.8.1.4
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-12-18 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 17:23 [PATCH 0/3 v2] Use lockless lists for smp_call_function_single() Jan Kara
2013-12-18 17:23 ` [PATCH 1/3] block: Stop abusing csd.list for fifo_time Jan Kara
2013-12-18 20:50 ` Jan Kara
2013-12-18 17:23 ` [PATCH 1/3] kernel: use lockless list for smp_call_function_single() Jan Kara
2013-12-18 17:23 ` [PATCH 2/3] block: Stop abusing csd.list for fifo_time Jan Kara
2013-12-18 17:23 ` [PATCH 2/3] block: Stop abusing rq->csd.list in blk-softirq Jan Kara
2013-12-18 20:50 ` Jan Kara [this message]
2013-12-18 17:23 ` [PATCH 3/3] " Jan Kara
2013-12-18 17:23 ` [PATCH 3/3] kernel: use lockless list for smp_call_function_single() Jan Kara
2013-12-18 20:51 ` Jan Kara
2013-12-18 20:50 ` [PATCH 0/3 v2] Use lockless lists " Jan Kara
2013-12-19 15:31 ` Jens Axboe
2014-01-07 15:47 ` Christoph Hellwig
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=20131218205058.GC13685@quack.suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.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