All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: lsf10-pc@lists.linuxfoundation.org
Cc: linux-scsi@vger.kernel.org, Ric Wheeler <rwheeler@redhat.com>,
	James Bottomley <James.Bottomley@suse.de>
Subject: [ATTEND] Want to attend LSF 2010
Date: Thu, 1 Jul 2010 14:04:30 -0400	[thread overview]
Message-ID: <20100701180430.GD2705@redhat.com> (raw)

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


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

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