[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/6] refactor RDMA live migration based on rsocket API
From: |
Michael S. Tsirkin |
Subject: |
Re: [PATCH 0/6] refactor RDMA live migration based on rsocket API |
Date: |
Tue, 27 Aug 2024 16:57:23 -0400 |
On Tue, Aug 27, 2024 at 04:15:42PM -0400, Peter Xu wrote:
> On Tue, Jun 04, 2024 at 08:14:06PM +0800, Gonglei wrote:
> > From: Jialin Wang <wangjialin23@huawei.com>
> >
> > Hi,
> >
> > This patch series attempts to refactor RDMA live migration by
> > introducing a new QIOChannelRDMA class based on the rsocket API.
> >
> > The /usr/include/rdma/rsocket.h provides a higher level rsocket API
> > that is a 1-1 match of the normal kernel 'sockets' API, which hides the
> > detail of rdma protocol into rsocket and allows us to add support for
> > some modern features like multifd more easily.
> >
> > Here is the previous discussion on refactoring RDMA live migration using
> > the rsocket API:
> >
> > https://lore.kernel.org/qemu-devel/20240328130255.52257-1-philmd@linaro.org/
> >
> > We have encountered some bugs when using rsocket and plan to submit them to
> > the rdma-core community.
> >
> > In addition, the use of rsocket makes our programming more convenient,
> > but it must be noted that this method introduces multiple memory copies,
> > which can be imagined that there will be a certain performance degradation,
> > hoping that friends with RDMA network cards can help verify, thank you!
> >
> > Jialin Wang (6):
> > migration: remove RDMA live migration temporarily
> > io: add QIOChannelRDMA class
> > io/channel-rdma: support working in coroutine
> > tests/unit: add test-io-channel-rdma.c
> > migration: introduce new RDMA live migration
> > migration/rdma: support multifd for RDMA migration
>
> This series has been idle for a while; we still need to know how to move
> forward.
What exactly is the question? This got a bunch of comments,
the first thing to do would be to address them.
> I guess I lost the latest status quo..
>
> Any update (from anyone..) on what stage are we in?
>
> Thanks,
> --
> Peter Xu