Re: [PATCH 0/6] refactor RDMA live migration based on rsocket API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 9/29/24 13:14, Michael S. Tsirkin wrote:
!-------------------------------------------------------------------|
   This Message Is From an External Sender
   This message came from outside your organization.
|-------------------------------------------------------------------!

On Sat, Sep 28, 2024 at 12:52:08PM -0500, Michael Galaxy wrote:
A bounce buffer defeats the entire purpose of using RDMA in these cases.
When using RDMA for very large transfers like this, the goal here is to map
the entire memory region at once and avoid all CPU interactions (except for
message management within libibverbs) so that the NIC is doing all of the
work.

I'm sure rsocket has its place with much smaller transfer sizes, but this is
very different.
To clarify, are you actively using rdma based migration in production? Stepping up
to help maintain it?

Yes, both Huawei and IONOS have both been contributing here in this email thread.

They are both using it in production.

- Michael




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux