linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: linux-kernel@vger.kernel.org, czoccolo@gmail.com,
	vgoyal@redhat.com, jmoyer@redhat.com, guijianfeng@cn.fujitsu.com,
	alex.shi@intel.com
Subject: Re: [RFC]cfq-iosched: fix a kbuild regression
Date: Wed, 17 Mar 2010 14:30:19 +0100	[thread overview]
Message-ID: <20100317133019.GV5768@kernel.dk> (raw)
In-Reply-To: <20100316025656.GA15390@sli10-desk.sh.intel.com>

On Tue, Mar 16 2010, Shaohua Li wrote:
> Alex Shi reported a kbuild regression which is about 10% performance lost.
> He bisected to this commit: 3dde36ddea3e07dd025c4c1ba47edec91606fec0.
> The reason is cfqq_close() can't find close cooperator. If we store the seek
> distance to the value before the commit like below, the regression fully goes
> away. If this is too invasive, just changing the cfq_rq_close() for the
> !for_preempt is ok too.

Corrado, any objections to widening the seek threshold?

> 
> Reported-by: Alex Shi <alex.shi@intel.com>
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> 
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index dee9d93..fcae456 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -46,7 +46,7 @@ static const int cfq_hist_divisor = 4;
>  #define CFQ_HW_QUEUE_MIN	(5)
>  #define CFQ_SERVICE_SHIFT       12
>  
> -#define CFQQ_SEEK_THR		(sector_t)(8 * 100)
> +#define CFQQ_SEEK_THR		(sector_t)(8 * 1024)
>  #define CFQQ_SECT_THR_NONROT	(sector_t)(2 * 32)
>  #define CFQQ_SEEKY(cfqq)	(hweight32(cfqq->seek_history) > 32/8)
>  

-- 
Jens Axboe


  reply	other threads:[~2010-03-17 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16  2:56 [RFC]cfq-iosched: fix a kbuild regression Shaohua Li
2010-03-17 13:30 ` Jens Axboe [this message]
2010-03-17 18:24   ` Corrado Zoccolo
2010-03-18  1:05     ` Shaohua Li
2010-03-18 16:55       ` Corrado Zoccolo
2010-03-19  7:57       ` Jens Axboe

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=20100317133019.GV5768@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=alex.shi@intel.com \
    --cc=czoccolo@gmail.com \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).