Re: [PATCH v2] vfio/type1: Limit DMA mappings per container

2019-04-03 Thread Alex Williamson
On Wed, 3 Apr 2019 15:24:26 -0400 Jerome Glisse wrote: > On Tue, Apr 02, 2019 at 10:15:38AM -0600, Alex Williamson wrote: > > Memory backed DMA mappings are accounted against a user's locked > > memory limit, including multiple mappings of the same memory. This > > accounting bounds the number o

Re: [PATCH v2] vfio/type1: Limit DMA mappings per container

2019-04-03 Thread Jerome Glisse
On Tue, Apr 02, 2019 at 10:15:38AM -0600, Alex Williamson wrote: > Memory backed DMA mappings are accounted against a user's locked > memory limit, including multiple mappings of the same memory. This > accounting bounds the number of such mappings that a user can create. > However, DMA mappings t

Re: [PATCH v2] vfio/type1: Limit DMA mappings per container

2019-04-03 Thread Cornelia Huck
On Tue, 02 Apr 2019 10:15:38 -0600 Alex Williamson wrote: > Memory backed DMA mappings are accounted against a user's locked > memory limit, including multiple mappings of the same memory. This > accounting bounds the number of such mappings that a user can create. > However, DMA mappings that a

Re: [PATCH v2] vfio/type1: Limit DMA mappings per container

2019-04-02 Thread Peter Xu
On Tue, Apr 02, 2019 at 10:15:38AM -0600, Alex Williamson wrote: > Memory backed DMA mappings are accounted against a user's locked > memory limit, including multiple mappings of the same memory. This > accounting bounds the number of such mappings that a user can create. > However, DMA mappings t

Re: [PATCH v2] vfio/type1: Limit DMA mappings per container

2019-04-02 Thread Auger Eric
Hi Alex, On 4/2/19 6:15 PM, Alex Williamson wrote: > Memory backed DMA mappings are accounted against a user's locked > memory limit, including multiple mappings of the same memory. This > accounting bounds the number of such mappings that a user can create. > However, DMA mappings that are not b