All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: "Xue, Chendi" <chendi.xue@intel.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Andrew Shewmaker <agshew@gmail.com>
Subject: Re: Checking on wip-blkin branch
Date: Tue, 09 Jun 2015 07:44:58 -0700	[thread overview]
Message-ID: <5576FBEA.8030805@redhat.com> (raw)
In-Reply-To: <C8CF870384EBCF4CAB89D2041A5C80B304B99DEA@SHSMSX101.ccr.corp.intel.com>

Hi Chendi,

On 06/09/2015 04:59 AM, Xue, Chendi wrote:
> Hi, Josh and Andrew
>
> Today, I applied wip-blkin branch to my 4 nodes ceph setup, and created zipkin-based lttng results successfully.
>
> Since we wanna using this latency analyzing methodology on further release or on keyvalue store and newstore.
> I am wondering what is the gap to merge blkin into master? Can I help to rebase to master, so we can merge this branch?

That'd be great! Andrew and I simply haven't had time to finish fixing
up the remaining issues. Running it through a rados suite showed some
more changes were necessary to handle more complicated osd usage -
you'll see several osd crashes in this rados suite run [1].

The code was looking fine to me, it just needs rebasing and debugging
so it can pass the rados test suite.

Thanks!
Josh

[1] 
http://pulpito.ceph.com/joshd-2015-03-25_17:29:16-rados-wip-blkin---blkin-multi/

  reply	other threads:[~2015-06-09 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 11:59 Checking on wip-blkin branch Xue, Chendi
2015-06-09 14:44 ` Josh Durgin [this message]
2015-06-16  7:02   ` Xue, Chendi
2015-06-16 17:13     ` Josh Durgin
2015-06-16 18:20       ` Josh Durgin

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=5576FBEA.8030805@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=agshew@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chendi.xue@intel.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.