Hi Chenbo, > -----Original Message----- > From: Xia, Chenbo <[email protected]> > Sent: Thursday, June 8, 2023 4:28 PM > To: Jiang, Cheng1 <[email protected]>; [email protected]; > Richardson, Bruce <[email protected]>; [email protected] > Cc: [email protected]; Hu, Jiayu <[email protected]>; Ding, Xuan > <[email protected]>; Ma, WenwuX <[email protected]>; Wang, YuanX > <[email protected]>; He, Xingguang <[email protected]> > Subject: RE: [PATCH v4] app/dma-perf: introduce dma-perf application > > > -----Original Message----- > > From: Jiang, Cheng1 <[email protected]> > > Sent: Thursday, June 8, 2023 1:03 PM > > To: [email protected]; Richardson, Bruce > > <[email protected]>; [email protected]; Xia, Chenbo > > <[email protected]> > > Cc: [email protected]; Hu, Jiayu <[email protected]>; Ding, Xuan > > <[email protected]>; Ma, WenwuX <[email protected]>; Wang, > YuanX > > <[email protected]>; He, Xingguang <[email protected]>; Jiang, > > Cheng1 <[email protected]> > > Subject: [PATCH v4] app/dma-perf: introduce dma-perf application > > > > There are many high-performance DMA devices supported in DPDK now, and > > these DMA devices can also be integrated into other modules of DPDK as > > accelerators, such as Vhost. Before integrating DMA into applications, > > developers need to know the performance of these DMA devices in > > various scenarios and the performance of CPUs in the same scenario, > > such as different buffer lengths. Only in this way can we know the > > target performance of the application accelerated by using them. This > > patch introduces a high-performance testing tool, which supports > > comparing the performance of CPU and DMA in different scenarios > > automatically with a pre-set config file. Memory Copy performance test are > supported for now. > > > > Signed-off-by: Cheng Jiang <[email protected]> > > Signed-off-by: Jiayu Hu <[email protected]> > > Signed-off-by: Yuan Wang <[email protected]> > > Acked-by: Morten Brørup <[email protected]> > > Some LONG_LINE warning could be fixed if it's friendly for searching logs. > > I didn't look into all details but overall it seems good. > > Acked-by: Chenbo Xia <[email protected]>
Sure, I will fix it in the next version. Thanks a lot. Cheng > > > --- > > v4: > > fixed inaccuracy of the memory footprint display; > > v3: > > fixed some typos; > > v2: > > added lcore/dmadev designation; > > added error case process; > > removed worker_threads parameter from config.ini; > > improved the logs; > > improved config file; > > > > app/meson.build | 1 + > > app/test-dma-perf/benchmark.c | 471 ++++++++++++++++++++++++++++ > > app/test-dma-perf/config.ini | 59 ++++ > > app/test-dma-perf/main.c | 567 ++++++++++++++++++++++++++++++++++ > > app/test-dma-perf/main.h | 69 +++++ > > app/test-dma-perf/meson.build | 17 + > > 6 files changed, 1184 insertions(+) > > create mode 100644 app/test-dma-perf/benchmark.c create mode 100644 > > app/test-dma-perf/config.ini create mode 100644 > > app/test-dma-perf/main.c create mode 100644 app/test-dma-perf/main.h > > create mode 100644 app/test-dma-perf/meson.build > >
