Re: [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation

2020-05-06 Thread Renata Saiakhova
Tuesday, May 5, 2020 1:01 PM To: Renata Saiakhova Cc: dev@dpdk.org ; ferruh.yi...@intel.com ; arybche...@solarflare.com Subject: Re: [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation 03/05/2020 18:26, Renata Saiakhova: > igb and ixgbe drivers allocate HW rings using rte_eth

Re: [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation

2020-05-05 Thread Thomas Monjalon
05/05/2020 13:19, Renata Saiakhova: > Hi Thomas, > > In our application dpdk port can be connected and disconnected: > > Connect: > new_port_id = netdev_dpdk_get_port_by_devargs(dpdk_port->pci_addr_str); > >if (!rte_eth_dev_is_valid_port(new_port_id)) { > /* Device not found in DPDK, a

Re: [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation

2020-05-05 Thread Thomas Monjalon
03/05/2020 18:26, Renata Saiakhova: > igb and ixgbe drivers allocate HW rings using rte_eth_dma_zone_reserve(), > which checks first if the memzone exists for a given name, consisting of port > id, queue_id, rx/tx direction, but not for the size, alignment, and socket_id. > If the memzone with a gi

[dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation

2020-05-04 Thread Renata Saiakhova
igb and ixgbe drivers allocate HW rings using rte_eth_dma_zone_reserve(), which checks first if the memzone exists for a given name, consisting of port id, queue_id, rx/tx direction, but not for the size, alignment, and socket_id. If the memzone with a given name exists it is returned, otherwise it