Re: [PATCH] e1000: set RX descriptor status in a separate operation

2022-07-04 Thread Jason Wang
On Mon, Jul 4, 2022 at 5:05 PM Ding Hui wrote: > > On 2022/7/4 15:10, Jason Wang wrote: > > > > 在 2022/6/29 17:40, Ding Hui 写道: > >> @@ -1013,6 +1013,9 @@ e1000_receive_iov(NetClientState *nc, const > >> struct iovec *iov, int iovcnt) > >> DBGOUT(RX, "Null RX descriptor!!\n"); > >>

Re: [PATCH] e1000: set RX descriptor status in a separate operation

2022-07-04 Thread Ding Hui
On 2022/7/4 15:10, Jason Wang wrote: 在 2022/6/29 17:40, Ding Hui 写道: @@ -1013,6 +1013,9 @@ e1000_receive_iov(NetClientState *nc, const struct iovec *iov, int iovcnt)   DBGOUT(RX, "Null RX descriptor!!\n");   }   pci_dma_write(d, base, &desc, sizeof(desc)); +   

Re: [PATCH] e1000: set RX descriptor status in a separate operation

2022-07-04 Thread Jason Wang
在 2022/6/29 17:40, Ding Hui 写道: The code of setting RX descriptor status field maybe work fine in previously, however with the update of glibc version, it shows two issues when guest using dpdk receive packets: 1. The dpdk has a certain probability getting wrong buffer_addr this impa

[PATCH] e1000: set RX descriptor status in a separate operation

2022-06-29 Thread Ding Hui
The code of setting RX descriptor status field maybe work fine in previously, however with the update of glibc version, it shows two issues when guest using dpdk receive packets: 1. The dpdk has a certain probability getting wrong buffer_addr this impact may be not obvious, such as lost a