From: Amit Prakash Shukla <amitprakashs@marvell.com>
To: fengchengwen <fengchengwen@huawei.com>,
Cheng Jiang <honest.jiang@foxmail.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Kevin Laatz <kevin.laatz@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: RE: [EXT] Re: [PATCH v2] app/dma-perf: support bi-directional transfer
Date: Wed, 28 Feb 2024 09:38:07 +0000 [thread overview]
Message-ID: <SJ0PR18MB5161B3F5D6BB9D4FC7EB5411C8582@SJ0PR18MB5161.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1e4fe21a-8732-779b-0def-938832bdae2d@huawei.com>
Hi Chengwen,
Please see my reply in-line.
Thanks
Amit Shukla
> -----Original Message-----
> From: fengchengwen <fengchengwen@huawei.com>
> Sent: Wednesday, February 28, 2024 12:34 PM
> To: Amit Prakash Shukla <amitprakashs@marvell.com>; Cheng Jiang
> <honest.jiang@foxmail.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>
> Cc: dev@dpdk.org; Jerin Jacob <jerinj@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Kevin Laatz <kevin.laatz@intel.com>; Bruce
> Richardson <bruce.richardson@intel.com>; Pavan Nikhilesh Bhagavatula
> <pbhagavatula@marvell.com>
> Subject: [EXT] Re: [PATCH v2] app/dma-perf: support bi-directional transfer
>
> External Email
>
> ----------------------------------------------------------------------
> Hi Amit and Gowrishankar,
>
> It's nature to support multiple dmadev test in one testcase, and the original
> framework supports it.
> But it seem we both complicated it when adding support for non-mem2mem
> dma test.
>
> The new added "direction" and "vchan_dev" could treat as the dmadev's
> private configure, some thing like:
>
> lcore_dma=lcore10@0000:00:04.2,vchan=0,dir=mem2dev,devtype=pcie,radd
> r=xxx,coreid=1,pfid=2,vfid=3
>
> then this bi-directional could impl only with config:
>
> lcore_dma=lcore10@0000:00:04.2,dir=mem2dev,devtype=pcie,raddr=xxx,cor
> eid=1,pfid=2,vfid=3,
> lcore11@0000:00:04.3,dir=dev2mem,devtype=pcie,raddr=xxx,coreid=1,pfid=
> 2,vfid=3
> so that the lcore10 will do mem2dev with device 0000:00:04.2, while lcore11
> will do dev2mem with device 0000:00:04.3.
Thanks for the suggestion. I will make the suggested changes and send the next version.
next prev parent reply other threads:[~2024-02-28 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 8:27 [PATCH] " Amit Prakash Shukla
2024-02-21 6:24 ` fengchengwen
2024-02-27 9:53 ` [EXT] " Amit Prakash Shukla
2024-02-27 19:26 ` [PATCH v2] " Amit Prakash Shukla
2024-02-28 7:03 ` fengchengwen
2024-02-28 9:38 ` Amit Prakash Shukla [this message]
2024-02-29 14:03 ` [EXT] " Amit Prakash Shukla
2024-03-01 1:46 ` fengchengwen
2024-03-01 8:31 ` [EXTERNAL] " Amit Prakash Shukla
2024-03-01 9:30 ` fengchengwen
2024-03-01 10:59 ` Amit Prakash Shukla
2024-03-07 13:41 ` fengchengwen
2024-02-29 14:14 ` [PATCH v3] " 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=SJ0PR18MB5161B3F5D6BB9D4FC7EB5411C8582@SJ0PR18MB5161.namprd18.prod.outlook.com \
--to=amitprakashs@marvell.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=gmuthukrishn@marvell.com \
--cc=honest.jiang@foxmail.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=pbhagavatula@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).