From: "J. Eric Ivancich" <ivancich@redhat.com>
To: Sage Weil <sweil@redhat.com>, g.marripudi@ssi.samsung.com
Cc: mbenjami@redhat.com, sjust@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: dm-clock queue
Date: Thu, 5 Nov 2015 17:19:21 -0500 [thread overview]
Message-ID: <563BD5E9.5060905@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1511021051450.24297@cobra.newdream.net>
Thank you, Sage. I will contact you in a separate message, Gunna, to
better understand your efforts and interests.
Eric
On 11/04/2015 05:35 PM, Sage Weil wrote:
> Hi Gunna, Eric-
>
> I wanted to make sure you were connected as we've talked to both of you
> independently about the new request queue in the OSD to support dm-clock
> and I want to make sure our efforts are coordinated. I thnk the first
> goal is probably to implement something that works and performs well for
> just a few request classes (clients, recovery, scrub, snaptrim).
> Eventually we'll also need to determine if/how to do so for a large client
> count so that we can do client qos. Just solving the first problem alone
> may be a big win, though: we hear lots of complaints about the effect of
> recovery on client io.
>
> Anyway, just wanted to make sure you two were connected and kick off the
> conversation.
>
> sage
>
next prev parent reply other threads:[~2015-11-05 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 22:35 dm-clock queue Sage Weil
2015-11-05 22:19 ` J. Eric Ivancich [this message]
2015-11-06 5:45 ` Gunna (Gunneswara) Marripudi-SSI
2015-11-06 5:58 ` Christoph Hellwig
2015-11-06 6:17 ` Gunna (Gunneswara) Marripudi-SSI
2015-11-06 6:22 ` Christoph Hellwig
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=563BD5E9.5060905@redhat.com \
--to=ivancich@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=g.marripudi@ssi.samsung.com \
--cc=mbenjami@redhat.com \
--cc=sjust@redhat.com \
--cc=sweil@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.