[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: New device for zero-copy VM memory access
From: |
Peter Maydell |
Subject: |
Re: RFC: New device for zero-copy VM memory access |
Date: |
Thu, 31 Oct 2019 14:52:47 +0000 |
On Thu, 31 Oct 2019 at 14:26, <address@hidden> wrote:
> As the author of Looking Glass, I also have to consider the maintenance
> and the complexity of implementing the vhost protocol into the project.
> At this time a complete Porthole client can be implemented in 150 lines
> of C without external dependencies, and most of that is boilerplate
> socket code. This IMO is a major factor in deciding to avoid vhost-user.
This is essentially a proposal that we should make our project and
code more complicated so that your project and code can be simpler.
I hope you can see why this isn't necessarily an argument that will hold
very much weight for us :-)
thanks
-- PMM
- RFC: New device for zero-copy VM memory access, geoff, 2019/10/29
- Re: RFC: New device for zero-copy VM memory access, geoff, 2019/10/29
- Re: RFC: New device for zero-copy VM memory access, Dr. David Alan Gilbert, 2019/10/30
- Re: RFC: New device for zero-copy VM memory access, geoff, 2019/10/30
- Re: RFC: New device for zero-copy VM memory access, geoff, 2019/10/31
- Re: RFC: New device for zero-copy VM memory access, Peter Maydell, 2019/10/31
- Re: RFC: New device for zero-copy VM memory access, Dr. David Alan Gilbert, 2019/10/31
- Re: RFC: New device for zero-copy VM memory access, geoff, 2019/10/31
- Re: RFC: New device for zero-copy VM memory access,
Peter Maydell <=
- Re: RFC: New device for zero-copy VM memory access, geoff, 2019/10/31
- Re: RFC: New device for zero-copy VM memory access, Dr. David Alan Gilbert, 2019/10/31