RE: [PATCH v3] app/dma-perf: calrify incorrect NUMA config

2024-11-20 Thread Varghese, Vipin
> > 20/03/2024 02:40, Vipin Varghese: > > In case incorrect NUMA configuration, the current commit shares > > 1) either `source or destination numa is greater` > > 2) instead of `actual NUMA` it is `acture NUMA` > > 3) uses `printf` instead of PRINT_ERR > > > > current patch changes the above t

Re: [PATCH v3] app/dma-perf: calrify incorrect NUMA config

2024-11-20 Thread Thomas Monjalon
20/03/2024 02:40, Vipin Varghese: > In case incorrect NUMA configuration, the current commit shares > 1) either `source or destination numa is greater` > 2) instead of `actual NUMA` it is `acture NUMA` > 3) uses `printf` instead of PRINT_ERR > > current patch changes the above to > 1) identify

RE: [EXTERNAL] [PATCH v3] app/dma-perf: calrify incorrect NUMA config

2024-11-19 Thread Gowrishankar Muthukrishnan
> Subject: [EXTERNAL] [PATCH v3] app/dma-perf: calrify incorrect NUMA config Looks good to me, with minor correction in subject: calrify -> clarify. Thanks, Gowrishankar

Re: [PATCH v3] app/dma-perf: calrify incorrect NUMA config

2024-11-19 Thread Thomas Monjalon
20/03/2024 02:40, Vipin Varghese: > In case incorrect NUMA configuration, the current commit shares > 1) either `source or destination numa is greater` > 2) instead of `actual NUMA` it is `acture NUMA` > 3) uses `printf` instead of PRINT_ERR > > current patch changes the above to > 1) identify

[PATCH v3] app/dma-perf: calrify incorrect NUMA config

2024-03-19 Thread Vipin Varghese
In case incorrect NUMA configuration, the current commit shares 1) either `source or destination numa is greater` 2) instead of `actual NUMA` it is `acture NUMA` 3) uses `printf` instead of PRINT_ERR current patch changes the above to 1) identify if source or|and destination is incorrect 2) f