public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	James Bottomley <James.Bottomley@suse.de>,
	lsf10-pc@lists.linuxfoundation.org, linux-scsi@vger.kernel.org
Subject: Re: [Lsf10-pc] [ATTEND] Want to attend LSF 2010
Date: Thu, 1 Jul 2010 14:40:43 -0400	[thread overview]
Message-ID: <20100701184043.GK3039@think> (raw)
In-Reply-To: <4C2CD9FE.8060707@redhat.com>

On Thu, Jul 01, 2010 at 02:10:06PM -0400, Ric Wheeler wrote:
> On 07/01/2010 02:04 PM, Vivek Goyal wrote:
> > Resending this mail. This time also CCing linux-scsi mailing list. Sorry
> > for the duplicate copy.
> >
> > Hi,
> >
> > I wanted to attend LSF 2010. Sepcifically I was interested in discussing
> > couple of things.
> >
> > - CFQ performance issues on higher end storage
> >          - Deadline outperforms CFQ on higher end storage (storage arrays
> >            and also on host based hardware RAID). I was wondering if there
> >            is a way to fix it or it is just design limitation. In the past
> >            Jens had mentioned that he wants to get rid of deadline also and
> >            be replaced with CFQ. Are we still targeting that and if yes,
> >            how to achieve that (some kind of auto tuning).
> >
> > - Max bandwidth IO controller
> >          - A basic proportional weight controller (blkio) based off CFQ is
> >            now in. Now there is also a need to implement throttling/max
> >            bandwidth controller. Wanted to get some ideas on how to go
> >            go about it and what is the best place to impement it. Implement
> >            it in CFQ or a new device mapper target or something else.
> >
> > Thanks
> > Vivek
> >
> 
> Thanks Vivek,
> 
> I know that this IO scheduling issue has been a hot issue for us in our 
> performance testing. We would love to figure out how to get CFQ to displace 
> deadline totally and definitely it would be very interesting to have a 
> conversation around what needs done/what can be done.
> 

I'll second that...one scheduler to rule them all.

-chris


  reply	other threads:[~2010-07-01 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 18:04 [ATTEND] Want to attend LSF 2010 Vivek Goyal
2010-07-01 18:10 ` Ric Wheeler
2010-07-01 18:40   ` Chris Mason [this message]
2010-07-01 18:54     ` [Lsf10-pc] " 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=20100701184043.GK3039@think \
    --to=chris.mason@oracle.com \
    --cc=James.Bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf10-pc@lists.linuxfoundation.org \
    --cc=rwheeler@redhat.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