Re: [dpdk-dev] [PATCH] vhost: fix iotlb pool out-of-memory handling

2018-01-26 Thread Maxime Coquelin
Hi Tiwei, On 01/26/2018 09:03 AM, Tiwei Bie wrote: On Thu, Jan 25, 2018 at 04:06:53PM +0100, Maxime Coquelin wrote: In the unlikely case the IOTLB memory pool runs out of memory, an issue may happen if all entries are used by the IOTLB cache, and an IOTLB miss happen. If the iotlb pending list

Re: [dpdk-dev] [PATCH] vhost: fix iotlb pool out-of-memory handling

2018-01-26 Thread Jens Freimann
On Thu, Jan 25, 2018 at 04:06:53PM +0100, Maxime Coquelin wrote: In the unlikely case the IOTLB memory pool runs out of memory, an issue may happen if all entries are used by the IOTLB cache, and an IOTLB miss happen. If the iotlb pending list is empty, then no memory is freed and allocation fail

Re: [dpdk-dev] [PATCH] vhost: fix iotlb pool out-of-memory handling

2018-01-26 Thread Tiwei Bie
On Thu, Jan 25, 2018 at 04:06:53PM +0100, Maxime Coquelin wrote: > In the unlikely case the IOTLB memory pool runs out of memory, > an issue may happen if all entries are used by the IOTLB cache, > and an IOTLB miss happen. If the iotlb pending list is empty, > then no memory is freed and allocatio

[dpdk-dev] [PATCH] vhost: fix iotlb pool out-of-memory handling

2018-01-25 Thread Maxime Coquelin
In the unlikely case the IOTLB memory pool runs out of memory, an issue may happen if all entries are used by the IOTLB cache, and an IOTLB miss happen. If the iotlb pending list is empty, then no memory is freed and allocation fails a second time. This patch fixes this by doing an IOTLB cache ran