All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Eric Ivancich" <ivancich@redhat.com>
To: sheng qiu <herbert1984106@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: How best to integrate dmClock QoS library into ceph codebase
Date: Thu, 29 Jun 2017 14:03:14 -0400	[thread overview]
Message-ID: <9c1d41e7-a218-d52b-f17f-0490c3a94d50@redhat.com> (raw)
In-Reply-To: <CAB7xdinUB6dTtc+ncfn7YAH0KKcAg03oxu778NbjHiafiqRnKQ@mail.gmail.com>

On 06/28/2017 02:55 PM, sheng qiu wrote:
> May I ask do you have any plan to implement client side logic for a
> true "D"mclock, seems to me know it's mclock on each individual OSD.
> And each client also has a common iops config. We are planing to
> working on that part and integrate with your current work.

That is not a high priority in the short-term. Our main goal with
integrating dmclock/mclock was to better manage priorities among
operation classes.

Developers at SK Telecom have done some work towards this, though. For
example, see here:

    https://github.com/ivancich/ceph/pull/1

Eric

  reply	other threads:[~2017-06-29 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 13:32 How best to integrate dmClock QoS library into ceph codebase J. Eric Ivancich
2017-04-04 16:00 ` Adam C. Emerson
2017-05-16  2:46 ` Ming Lin
2017-05-16 12:29   ` J. Eric Ivancich
2017-05-16 17:59     ` Ming Lin
2017-06-21 17:38     ` sheng qiu
2017-06-21 21:04       ` J. Eric Ivancich
2017-06-27 21:21         ` sheng qiu
2017-06-28 18:33           ` J. Eric Ivancich
2017-06-28 18:55             ` sheng qiu
2017-06-29 18:03               ` J. Eric Ivancich [this message]
2017-07-04 12:35                 ` Jin Cai
2017-07-05 22:06                   ` J. Eric Ivancich
2017-07-11 18:14             ` sheng qiu
2017-07-27 20:24               ` J. Eric Ivancich

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=9c1d41e7-a218-d52b-f17f-0490c3a94d50@redhat.com \
    --to=ivancich@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=herbert1984106@gmail.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.