From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 884D5A0032; Fri, 21 Oct 2022 15:28:59 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2C35041147; Fri, 21 Oct 2022 15:28:59 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id C57D4400D6 for ; Fri, 21 Oct 2022 15:28:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666358937; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HJ5xjEqAgeuxgjPFMCSiT7NZWetKUioMq2YAvgSfnrA=; b=FSs4V0+cqC1YEnkC8VgWpfvcDY73jQeldR6u0CAmZ4sI3AJQGbSA3Go2TI8YuKWXlCOWYH J2QANcYhiNGWaLgrSNo/eDoFyL531RLXn60ToqvtepYjxPa6m0aOjs0N4Y5Pn/uvUEZKCx KvDj+/EtqWoV2cuFlbMQ50GLItQ89/I= Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-563-rlfDz5O1OrCWwb6UOH5gcA-1; Fri, 21 Oct 2022 09:28:56 -0400 X-MC-Unique: rlfDz5O1OrCWwb6UOH5gcA-1 Received: by mail-pj1-f72.google.com with SMTP id px13-20020a17090b270d00b0020aa188aae8so1229726pjb.8 for ; Fri, 21 Oct 2022 06:28:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HJ5xjEqAgeuxgjPFMCSiT7NZWetKUioMq2YAvgSfnrA=; b=pEVX+gkNvS3KoQNes2IIn1QSP+kRj/et9PAma8OG73Jr1TMHR4/gwwM6g0JOie2sJv fwkZYRb8mhkY1P1pNhkRLwH491lIFr1xwW0qZ+exeKxmUfsxnVwMYeYk17gk4hleM+yO TpAi+8j8tsYQrZt/CtOspf4NGWXYHoRp6h50hvPNlzuSH+vs7C7LjH/RNwcUe++I9rS5 GQlIxt7nyfwsRZXB5CrwzRa+gp5ARFXOrHWy+8FQBXgIVfQEEMWA8E1Esb10V/VhJGn4 JIDn3TLznLqVEC1cdQDc+Q2/2FxNxBw9AJUSW3cIMCX8c1N2WG7IvR33+OygGSdhFPFZ gqdg== X-Gm-Message-State: ACrzQf3wlvTEHlWICuKoGH86V/KRjkjuc8klWk60ctywbiA0D4R8cY0Z 6m+S/Z663Va1FKYzEF2N2Rjp+rg6M3J5OQpzSqdVF+LgXxaYwMhq0IAgdd7JSysxsR7JW0kCxch 8SHxAxlbNKhLUYkdQ4J8= X-Received: by 2002:a17:902:bf46:b0:179:eba5:90ba with SMTP id u6-20020a170902bf4600b00179eba590bamr19312066pls.16.1666358935127; Fri, 21 Oct 2022 06:28:55 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5cbnvBRl9B7FCxg6JXPADNvJyu6hUm0GuDfwnyflsFCKFhwh5zQJWFpxbeTi5OlaAIcGZbFLTiqLsLxBQxsRo= X-Received: by 2002:a17:902:bf46:b0:179:eba5:90ba with SMTP id u6-20020a170902bf4600b00179eba590bamr19312038pls.16.1666358934842; Fri, 21 Oct 2022 06:28:54 -0700 (PDT) MIME-Version: 1.0 References: <20220915154758.688-1-cheng1.jiang@intel.com> <20221018064249.26158-1-cheng1.jiang@intel.com> In-Reply-To: <20221018064249.26158-1-cheng1.jiang@intel.com> From: David Marchand Date: Fri, 21 Oct 2022 15:28:43 +0200 Message-ID: Subject: Re: [RFC v3] app/dma-perf: introduce dma-perf application To: Cheng Jiang Cc: thomas@monjalon.net, bruce.richardson@intel.com, mb@smartsharesystems.com, dev@dpdk.org, jiayu.hu@intel.com, xuan.ding@intel.com, wenwux.ma@intel.com, yuanx.wang@intel.com, yvonnex.yang@intel.com, xingguang.he@intel.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, Oct 18, 2022 at 9:22 AM Cheng Jiang wrote: > > 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 > Signed-off-by: Jiayu Hu > Signed-off-by: Yuan Wang > Acked-by: Morten Br=C3=B8rup > --- > v3: improved nr_buf calculation and added support for getting subprocess = exit status > v2: fixed some CI issues. There is still at least one build issue. --=20 David Marchand