From: Vivek Goyal <vgoyal@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jens Axboe <axboe@kernel.dk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CFQ: clarify code touching 'cic_index' a bit
Date: Wed, 3 Aug 2011 17:00:54 -0400 [thread overview]
Message-ID: <20110803210054.GD32385@redhat.com> (raw)
In-Reply-To: <1312400476.22854.1.camel@t41.thuisdomein>
On Wed, Aug 03, 2011 at 09:41:12PM +0200, Paul Bolle wrote:
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> block/cfq-iosched.c | 17 ++++++++---------
> 1 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index 1f96ad6..601a24c 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -3948,39 +3948,38 @@ static void cfq_exit_queue(struct elevator_queue *e)
> kfree(cfqd);
> }
>
> -static int cfq_alloc_cic_index(void)
> +static int cfq_alloc_cic_index(int *cic_index)
Changing function signature does not make it any more clear.
> {
> - int index, error;
> + int error;
>
> do {
> if (!ida_pre_get(&cic_index_ida, GFP_KERNEL))
> return -ENOMEM;
>
> spin_lock(&cic_index_lock);
> - error = ida_get_new(&cic_index_ida, &index);
> + error = ida_get_new(&cic_index_ida, cic_index);
> spin_unlock(&cic_index_lock);
> if (error && error != -EAGAIN)
> return error;
> } while (error);
>
> - return index;
> + return 0;
> }
>
> static void *cfq_init_queue(struct request_queue *q)
> {
> struct cfq_data *cfqd;
> - int i, j;
> + int i, j, cic_index;
If you want it little more clear then rename i to cic_index.
Thanks
Vivek
> struct cfq_group *cfqg;
> struct cfq_rb_root *st;
>
> - i = cfq_alloc_cic_index();
> - if (i < 0)
> + if (cfq_alloc_cic_index(&cic_index))
> return NULL;
>
> cfqd = kmalloc_node(sizeof(*cfqd), GFP_KERNEL | __GFP_ZERO, q->node);
> if (!cfqd) {
> spin_lock(&cic_index_lock);
> - ida_remove(&cic_index_ida, i);
> + ida_remove(&cic_index_ida, cic_index);
> spin_unlock(&cic_index_lock);
> return NULL;
> }
> @@ -3989,7 +3988,7 @@ static void *cfq_init_queue(struct request_queue *q)
> * Don't need take queue_lock in the routine, since we are
> * initializing the ioscheduler, and nobody is using cfqd
> */
> - cfqd->cic_index = i;
> + cfqd->cic_index = cic_index;
>
> /* Init root service tree */
> cfqd->grp_service_tree = CFQ_RB_ROOT;
> --
> 1.7.6
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2011-08-03 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 19:41 [PATCH] CFQ: clarify code touching 'cic_index' a bit Paul Bolle
2011-08-03 21:00 ` Vivek Goyal [this message]
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=20110803210054.GD32385@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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.