ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Sage Weil <sage@inktank.com>
Cc: greg@inktank.com, ceph-devel@vger.kernel.org
Subject: Re: messenger changes
Date: Thu, 29 May 2014 18:04:50 -0400 (EDT)	[thread overview]
Message-ID: <1079621891.156.1401401090133.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1405291345580.20692@cobra.newdream.net>

Hi Sage,

Sure, I'll join the core standup.  I think you have the right ideas, I'll give
it some more thought as well, before tomorrow's meeting.

Thanks,

Matt

----- "Sage Weil" <sage@inktank.com> wrote:

> Hey Matt,
> 
> Can you join us for the core standup tomorrow, or shortly after, to
> sycn 
> up on the messenger changes needed for xio?
> 
> I've taken most of the generic messenger refactoring and changes that
> I 
> see that aren't yet xio-specific and pulled them into wip-msgr:
> 
> 	https://github.com/ceph/ceph/pull/1883
> 
> The main things I see now that are blocking the rest of the xio
> stuff:
> 
>  - xio specific code in the buffer class
> 
>  - the Message completion hook and other stuff needs to be separated
> out 
> into a separate patch that goes ahead of the other pieces
> 
>  - I don't think creating multiple Messenger instances for all of the
> OSD, 
> mon, etc is going to work well.  We need to figure out a generic way
> to 
> instantiate them without adding support that is specific to every 
> subsystem/client/daemon/whatever.  Probably this means passing an
> address 
> type to the Messenger::create() method, or something similar. For now,
> I 
> think we can focus on a single transport for each part of the system 
> (e.g., osd<->osd) and not worry about multiprotocol support.  That
> will 
> get us to something usable much sooner.
> 
> sage
> 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

      reply	other threads:[~2014-05-29 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 20:46 messenger changes Sage Weil
2014-05-29 22:04 ` Matt W. Benjamin [this message]

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=1079621891.156.1401401090133.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).