The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@gmx.de>
To: Aaron Carroll <aaronc@gelato.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: deadline unfairness
Date: Sat, 22 Mar 2008 14:06:01 +0100	[thread overview]
Message-ID: <200803221406.02621.bernd-schubert@gmx.de> (raw)
In-Reply-To: <47E4F6F7.40401@gelato.unsw.edu.au>

Hello Aron,

On Saturday 22 March 2008, Aaron Carroll wrote:
> Bernd Schubert wrote:
> > Hello,
> >
> > some it seems the deadline scheduler is rather unfair. Below is an
> > example of md-raid6 initialization of md3, md4 and md5. All three
> > md-devices do share the same blockdevices (we have patched md to allow
> > parallel rebuild of shared block devices, since for us the cpu is the
> > bottleneck and not the block device).
> >
> > All rebuilds started basically at the same time, as you can see, md3 is
> > already done and now md4 rebuilds substantially faster than md5.
> > [..]
> > This is basically with a 2.6.22 kernel + lustre + md-backports, but
> > nothing done to the scheduler.
>
> Hi Bernd,
>
> There is a deadline bug in pre-2.6.24 kernels where lower-sector requests
> can starve higher-sector requests; you might be hitting this bug.  It was
> fixed by commit: 6f5d8aa6382eef2b26032c88656270bdae7f0c42

thanks a lot for your help! I will build a new kernel later on today and then 
report back if it helps. Commit dfb3d72a9aa519672c9ae06f0d2f93eccb35482f also 
looks useful...

Thanks again,
Bernd

  reply	other threads:[~2008-03-22 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 11:25 deadline unfairness Bernd Schubert
2008-03-22 12:09 ` Aaron Carroll
2008-03-22 13:06   ` Bernd Schubert [this message]
2008-03-24 16:44     ` Bernd Schubert
2008-03-22 23:38 ` Jan Engelhardt
2008-03-24 16:16   ` Bernd Schubert

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=200803221406.02621.bernd-schubert@gmx.de \
    --to=bernd-schubert@gmx.de \
    --cc=aaronc@gelato.unsw.edu.au \
    --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