From: "Matt W. Benjamin" <matt@cohortfs.com>
To: Gregory Farnum <greg@inktank.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>, Sage Weil <sage@inktank.com>
Subject: Re: XioMessenger (RDMA) Status Update
Date: Tue, 13 May 2014 21:30:39 -0400 (EDT) [thread overview]
Message-ID: <731499372.186.1400031039363.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <774348207.178.1400024312462.JavaMail.root@thunderbeast.private.linuxbox.com>
Hi Greg,
1. there isn't support for for mark_down() yet (!), but we're working
on it. I've had good discussions with the Accelio team regarding exposing
explicit channel and flow control interfaces, which round out that topic
as we were exploring it.
2. the big changes in this push are major cleanups and bug fixes, plus
much wider integration with the user space code. my #1 action item from
our last convo was to first extend Xio coverage everywhere, and in particular,
add support for intra-cluster messaging over Xio.
2.1 on the cleanups and bugs front, starting with biggest, I finished support
for peer identification, using a small api change to Accelio (it's now on the
official Accelio for_next branch). a Connection refcnt underrun is fixed. then
I added a mechanism to bypass Accelio for intra-server messages, using a special
singleton connection. I cleaned up, but didn't deepen, feature support, as a
temporary measure. There's lot's of cleanup and various fixes in ceph_osd, too.
2.2 then, I did first cut integration with the MDS, and while at it, the Client
module as well. I've only started verifying, but so far it looks like the
intra-cluster messaging paths work, and a client workload may work--more fixes
likely forthcoming.
I have a plan to get at least the starter policy interfaces like mark_down and
mark_down_all shorty.
Matt
----- "Gregory Farnum" <greg@inktank.com> wrote:
> On Tue, May 13, 2014 at 2:08 PM, Matt W. Benjamin <matt@cohortfs.com>
> wrote:
> > Hi Ceph Devs,
> >
> > I've pushed two Ceph+Accelio branches, xio-firefly and
> xio-firefly-cmake to our
> > public ceph repository
> https://github.com/linuxbox2/linuxbox-ceph.git .
> >
> > These branches are pulled up to the HEAD of ceph/firefly, and also
> have improvements
> > to XioMessenger which allow:
> >
> > 1. operation of (at least) a minimal Ceph Mon and OSD cluster over
> Xio messaging alone
> > 2. initial support for Accelio in the MDS server and
> Client/libcephfs (not formally tested)
> >
> > There are some new config options:
> >
> > (global addr) "rdma local" sets a local rdma interface address
> > (global bool) "cluster rdma" selects Accelio for intra-cluster
> communication
> > (global bool) "client rdma" selecs Accelio for libcephfs
> communications
> >
> > These changes haven't been strenuously tested, we'll expect to have
> additional information
> > and likely new, simple rados bench results against this code in the
> next several days,
> > at latest.
>
> Can you talk about what structural changes you've made since the last
> branch? :) Is there support for mark_down or some of the other things
> we've discussed?
> -Greg
--
Matt Benjamin
CohortFS, LLC.
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://cohortfs.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2014-05-14 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <774348207.178.1400024312462.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-05-14 1:30 ` Matt W. Benjamin [this message]
2014-05-14 2:55 ` XioMessenger (RDMA) Status Update Gregory Farnum
[not found] <1143714307.164.1400015257404.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-05-13 21:08 ` Matt W. Benjamin
2014-05-13 21:10 ` Mark Nelson
2014-05-13 22:54 ` Gregory Farnum
2014-05-16 18:21 ` Sage Weil
2014-05-16 19:03 ` Gregory Farnum
2014-05-16 19:15 ` Sage Weil
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=731499372.186.1400031039363.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@cohortfs.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sage@inktank.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.