Hi,
Would you please provide a list of impacted APIs, thus we can check if our
code has further issues. b.t.w, we are now using dpdk 18.11.
Thanks.
2019年8月14日 下午11:09，Tiwei Bie 写道：
On Wed, Aug 14, 2019 at 03:31:09AM +, He Peng wrote:
Hi，
We found that *rte_vhost_rx_queue_count
Hi，
We found that *rte_vhost_rx_queue_count* is not protected by vq->access_lock,
and the access to vq->avail->idx is not thread-safe, since at the same time, the
vq->avail might be
set by *vring_invalidate* when some vhost-user messages arrived, such as
VRING_SET_ADDRESS,
VRING_SET_MEM_TAB
Hi,
In dpdk 16.11, most of mlnx device APIs except RX/TX are protected by a private
lock. In DPDK 18.11, these locks are removed, from the code it seems this is
due to all APIs will create a disposable socket and the socket will be used to
set/get specific device features, and will be close
2019年7月16日 下午10:19，He Peng 写道：
Hi，
2019年7月16日 下午9:51，Stephen Hemminger 写道：
On Wed, 17 Jul 2019 02:26:57 GMT
He Peng wrote:
Hi,
In file dpdk/lib/librte_eal/common/rte_malloc.c:
/*
* Allocate memory on default heap.
*/
void *
rte_malloc(const char *type, size_t size, unsigned
Hi，
2019年7月16日 下午9:51，Stephen Hemminger 写道：
On Wed, 17 Jul 2019 02:26:57 GMT
He Peng wrote:
Hi,
In file dpdk/lib/librte_eal/common/rte_malloc.c:
/*
* Allocate memory on default heap.
*/
void *
rte_malloc(const char *type, size_t size, unsigned align)
{
return rte_malloc_socket(type
Hi,
In file dpdk/lib/librte_eal/common/rte_malloc.c:
/*
* Allocate memory on default heap.
*/
void *
rte_malloc(const char *type, size_t size, unsigned align)
{
return rte_malloc_socket(type, size, align, SOCKET_ID_ANY);
}
/*
* Allocate zero'd memory on specified heap.
*/
void *
rte_zmalloc_s
Hi, Sabu and Bruce:
I saw your post in the mailing list about I350 fails to send packets,
however it is posted about one year ago.
Now we have encountered the same issue.
We are now building a forwarding device which forwards packets between 2
I350 ports, and we observe that the
7 matches
Mail list logo
