On Thu, May 09, 2019 at 02:12:55AM -0700, Stefan Hajnoczi wrote:
> On Mon, May 06, 2019 at 12:04:06PM +0300, Maxim Levitsky wrote:
> > On top of that, it is expected that newer hardware will support the PASID
> > based
> > device subdivision, which will allow us to _directly_ pass through the
> >
On Mon, May 06, 2019 at 12:04:06PM +0300, Maxim Levitsky wrote:
> On top of that, it is expected that newer hardware will support the PASID
> based
> device subdivision, which will allow us to _directly_ pass through the
> submission queues of the device and _force_ us to use the NVME protocol
On 06/05/19 07:57, Christoph Hellwig wrote:
>
> Or to put it into another way: unless your paravirt interface requires
> zero specific changes to the core nvme code it is not acceptable at all.
I'm not sure it's possible to attain that goal, however I agree that
putting the control plane in the
On Mon, May 06, 2019 at 05:57:52AM -0700, Christoph Hellwig wrote:
> > However, similar to the (1), when the driver will support the devices with
> > hardware based passthrough, it will have to dedicate a bunch of queues to
> > the
> > guest, configure them with the appropriate PASID, and then
On Mon, May 06, 2019 at 12:04:06PM +0300, Maxim Levitsky wrote:
> 1. Frontend interface (the interface that faces the guest/userspace/etc):
>
> VFIO/mdev is just way to expose a (partially) software defined PCIe device to
> a
> guest.
>
> Vhost on the other hand is an interface that is
On Fri, 2019-05-03 at 14:18 +0200, Christoph Hellwig wrote:
> I simply don't get the point of this series.
>
> MDEV is an interface for exposing parts of a device to a userspace
> program / VM. But that this series appears to do is to expose a
> purely software defined nvme controller to
I simply don't get the point of this series.
MDEV is an interface for exposing parts of a device to a userspace
program / VM. But that this series appears to do is to expose a
purely software defined nvme controller to userspace. Which in
principle is a good idea, but we have a much better
Hi everyone!
In this patch series, I would like to introduce my take on the problem of doing
as fast as possible virtualization of storage with emphasis on low latency.
For more information for the inner working you can look at V1 of the submission
at
https://lkml.org/lkml/2019/3/19/458
***
8 matches
Mail list logo
