From: Amit Prakash Shukla <amitprakashs@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Cheng Jiang <honest.jiang@foxmail.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: RE: [PATCH v2] app/dma-perf: per device config support
Date: Tue, 12 Nov 2024 15:26:51 +0000 [thread overview]
Message-ID: <PH0PR18MB5167F2158F3B66F46B2C2498C8592@PH0PR18MB5167.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB516736FBEA2C57D803A384B4C8432@PH0PR18MB5167.namprd18.prod.outlook.com>
Hi Thomas,
Gentle ping.
Thanks,
Amit Shukla
> -----Original Message-----
> From: Amit Prakash Shukla
> Sent: Monday, October 21, 2024 2:07 PM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Jerin Jacob <jerinj@marvell.com>; Vamsi Krishna
> Attunuru <vattunuru@marvell.com>; Anoob Joseph <anoobj@marvell.com>;
> Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>; Cheng Jiang
> <honest.jiang@foxmail.com>; Chengwen Feng
> <fengchengwen@huawei.com>
> Subject: RE: [PATCH v2] app/dma-perf: per device config support
>
> Hi Thomas,
>
> Gentle ping.
>
> Could you please consider merging this patch.
>
> Thanks,
> Amit Shukla
>
> > -----Original Message-----
> > From: Amit Prakash Shukla <amitprakashs@marvell.com>
> > Sent: Thursday, September 26, 2024 5:43 PM
> > To: Cheng Jiang <honest.jiang@foxmail.com>; Chengwen Feng
> > <fengchengwen@huawei.com>
> > Cc: dev@dpdk.org; Jerin Jacob <jerinj@marvell.com>; Vamsi Krishna
> > Attunuru <vattunuru@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>;
> > Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>; Amit
> Prakash
> > Shukla <amitprakashs@marvell.com>
> > Subject: [PATCH v2] app/dma-perf: per device config support
> >
> > Add support to configure device specific config parameters for a testcase.
> > Example:
> >
> > lcore_dma0=lcore=11,dev=0000:00:04.1,dir=mem2dev,raddr=0x300000000,
> > coreid=1,pfid=2,vfid=3
> > lcore_dma1=lcore=12,dev=0000:00:04.2,dir=dev2mem,raddr=0x200000000,
> > coreid=3,pfid=2,vfid=1
> >
> > Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> > Acked-by: Chengwen Feng <fengchengwen@huawei.com>
> > ---
> > v2:
> > - Resolved review comments.
> >
> > app/test-dma-perf/benchmark.c | 318
> > +++++++++++++++++++++-------------
> > app/test-dma-perf/config.ini | 30 ++--
> > app/test-dma-perf/main.c | 199 ++++++---------------
> > app/test-dma-perf/main.h | 20 ++-
> > doc/guides/tools/dmaperf.rst | 107 +++++++++---
> > 5 files changed, 360 insertions(+), 314 deletions(-)
> >
>
> <snip>
next prev parent reply other threads:[~2024-11-12 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 13:51 [PATCH] " Amit Prakash Shukla
2024-09-05 3:49 ` fengchengwen
2024-09-26 12:13 ` [PATCH v2] " Amit Prakash Shukla
2024-10-21 8:37 ` Amit Prakash Shukla
2024-11-12 15:26 ` Amit Prakash Shukla [this message]
2024-11-12 15:30 ` Thomas Monjalon
2024-11-12 15:58 ` [EXTERNAL] " Amit Prakash Shukla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR18MB5167F2158F3B66F46B2C2498C8592@PH0PR18MB5167.namprd18.prod.outlook.com \
--to=amitprakashs@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=gmuthukrishn@marvell.com \
--cc=honest.jiang@foxmail.com \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
--cc=vattunuru@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).