From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
abali@us.ibm.com, "Michael R. Hines" <mrhines@us.ibm.com>,
gokul@us.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH RDMA support v2: 4/6] initialize RDMA options when QEMU first runs on command-line
Date: Wed, 6 Mar 2013 05:10:01 -0500 (EST) [thread overview]
Message-ID: <593216899.3131612.1362564601854.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130221201207.GC29168@redhat.com>
> On Tue, Feb 19, 2013 at 09:42:45AM +0100, Paolo Bonzini wrote:
> > Il 19/02/2013 07:00, Michael R. Hines ha scritto:
> > > Yes, this is done at migration time (see functions
> > > "rdma_client_init"
> > > and "rdma_server_prepare()")
> > >
> > > To explain the host and port:
> > >
> > > The separate host and port are used by the library "librdmacm". This
> > > library performs a network translation between the IP address and a
> > > unique infiniband user-level Port number and the physical
> > > interface that has the RDMA capabilities. This library requires an
> > > IP address and port bound specifically to the requested RDMA interface
> > > to work.
> > >
> > > The patch does not assume that the network interface used for TCP
> > > traffic will necessarily be the same as the interface used for
> > > RDMA traffic.
> >
> > Of course the best thing to do would be to have all traffic on the
> > RDMA interface... :)
>
> You can't do this with infiniband, RDMA is only possible once the
> connection is established.
Sorry, I meant on the infiniband interface.
Right now Michael (Hines)'s code needs two sockets, one for TCP and
one for RDMA. If I understand correctly, the rdmacm library does not
need a separate address to set up the connection, that's just an
artifact of the implementation.
Whatever goes on in the TCP socket can be done on RDMA after establishing
the connection, or can be done with SEND.
Paolo
>
> > > Alternatively, this host and port could be specified using the
> > > QMP
> > > "migrate" command, but this command already has the URI for the
> > > TCP side
> > > of things reserved.
> > >
> > > If you guys like, we could specify a *second* URI on the QMP
> > > command
> > > line - we don't really have a preference.
> > >
> > > Either way is fine........ whatever the consensus is.
> > >
> > > - Michael
> >
>
parent reply other threads:[~2013-03-06 10:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20130221201207.GC29168@redhat.com>]
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=593216899.3131612.1362564601854.JavaMail.root@redhat.com \
--to=pbonzini@redhat.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=gokul@us.ibm.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.