mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: Jens Axboe <axboe@kernel.dk>, Jeff Moyer <jmoyer@redhat.com>,
	Corrado Zoccolo <czoccolo@gmail.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CFQ: delay getting cfq group at the very point we really need it
Date: Fri, 16 Jul 2010 09:52:11 -0400	[thread overview]
Message-ID: <20100716135211.GB15382@redhat.com> (raw)
In-Reply-To: <4C3E6B78.6070808@cn.fujitsu.com>

On Thu, Jul 15, 2010 at 09:59:20AM +0800, Gui Jianfeng wrote:
> Delay searching or allocating a cfq group at the very point that
> we really need it. This change would save some cycles every time
> we're getting a cfq queue.
> 
> Signed-off-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
> ---
>  block/cfq-iosched.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index eb4086f..9b0cf13 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -2820,10 +2820,8 @@ cfq_find_alloc_queue(struct cfq_data *cfqd, bool is_sync,
>  {
>  	struct cfq_queue *cfqq, *new_cfqq = NULL;
>  	struct cfq_io_context *cic;
> -	struct cfq_group *cfqg;
>  
>  retry:
> -	cfqg = cfq_get_cfqg(cfqd, 1);
>  	cic = cfq_cic_lookup(cfqd, ioc);
>  	/* cic always exists here */
>  	cfqq = cic_to_cfqq(cic, is_sync);
> @@ -2852,6 +2850,9 @@ retry:
>  		}
>  
>  		if (cfqq) {
> +			struct cfq_group *cfqg;
> +
> +			cfqg = cfq_get_cfqg(cfqd, 1);
>  			cfq_init_cfqq(cfqd, cfqq, current->pid, is_sync);

Gui, I noticed that once we have setup a cfqq and cfqg, for subequent
requests we should not come into this function at all because in 
cfq_set_request(), cic will have pointer to cfqq.

So I am not sure in what call path there is substantial saving but anyway,
it should not harm moving cfq_get_cfqg() call down and call it after
cfqq has been allocated.

Acked-by: Vivek Goyal <vgoyal@redhat.com>

Thanks
Vivek

      reply	other threads:[~2010-07-16 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  1:59 Gui Jianfeng
2010-07-16 13:52 ` 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=20100716135211.GB15382@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=czoccolo@gmail.com \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=jmoyer@redhat.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

Powered by JetHome