Re: [PATCH] vhost: introduce O(1) vq metadata cache

2016-12-14 Thread Jason Wang
On 2016年12月14日 16:14, kbuild test robot wrote: Hi Jason, [auto build test WARNING on vhost/linux-next] [also build test WARNING on v4.9 next-20161214] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] vhost: introduce O(1) vq metadata cache

2016-12-14 Thread Jason Wang
On 2016年12月14日 16:14, kbuild test robot wrote: Hi Jason, [auto build test WARNING on vhost/linux-next] [also build test WARNING on v4.9 next-20161214] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] vhost: introduce O(1) vq metadata cache

2016-12-14 Thread kbuild test robot
Hi Jason, [auto build test WARNING on vhost/linux-next] [also build test WARNING on v4.9 next-20161214] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] vhost: introduce O(1) vq metadata cache

2016-12-14 Thread kbuild test robot
Hi Jason, [auto build test WARNING on vhost/linux-next] [also build test WARNING on v4.9 next-20161214] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] vhost: introduce O(1) vq metadata cache

2016-12-13 Thread Jason Wang
When device IOTLB is enabled, all address translations were stored in interval tree. O(lgN) searching time could be slow for virtqueue metadata (avail, used and descriptors) since they were accessed much often than other addresses. So this patch introduces an O(1) array which points to the

[PATCH] vhost: introduce O(1) vq metadata cache

2016-12-13 Thread Jason Wang
When device IOTLB is enabled, all address translations were stored in interval tree. O(lgN) searching time could be slow for virtqueue metadata (avail, used and descriptors) since they were accessed much often than other addresses. So this patch introduces an O(1) array which points to the