[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation
From: |
Yuval Shaia |
Subject: |
Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation |
Date: |
Thu, 21 Dec 2017 09:27:51 +0200 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
> >
> > > What happens if guest attempts to register all its memory?
> > >
> >
> > Then we loose, is not different from bare metal, reg_mr will pin all the
> > RAM.
>
> We need to find a way to communicate to guests about amount
> of memory they can pin.
dev_caps.max_mr_size is the way device limits guest driver.
This value is controlled by the command line argument dev-caps-max-mr-size
so we should be fine (btw, default value is 1<<32).
>
> > However this is only one scenario, and hopefully not much used
> > for RoCE. (I know IPoIB does that, but it doesn't make sense to use it with
> > RoCE).
>
> SRP does it too AFAIK.
>
Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Michael S. Tsirkin, 2017/12/19
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Marcel Apfelbaum, 2017/12/20
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Michael S. Tsirkin, 2017/12/20
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation,
Yuval Shaia <=
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Michael S. Tsirkin, 2017/12/21
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Marcel Apfelbaum, 2017/12/21
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Michael S. Tsirkin, 2017/12/21
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Yuval Shaia, 2017/12/21
- Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Marcel Apfelbaum, 2017/12/21
Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation, Yuval Shaia, 2017/12/20