From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@amd.com>
Cc: cheng1.jiang@intel.com, stable@dpdk.org, anoobj@marvell.com,
jerinj@marvell.com, dev@dpdk.org,
"lihuisong (C)" <lihuisong@huawei.com>
Subject: Re: [PATCH v3] app/dma-perf: fix physical address seg-fault
Date: Tue, 14 Nov 2023 15:27:26 +0100 [thread overview]
Message-ID: <1958005.yKVeVyVuyW@thomas> (raw)
In-Reply-To: <aa2763c6-632f-97ed-a25d-73bf42defeba@huawei.com>
24/10/2023 04:16, lihuisong (C):
>
> 在 2023/10/19 12:19, Vipin Varghese 写道:
> > do_cpu_mem_copy uses DPDK API rte_mbuf_data_iova to return
> > the start of the virtual address for both src and dst.
> > But in case of iova mode set as PA, this results in seg-fault.
> > This is because rte_memcpy uses VA address and not PA.
> >
> > This fix invokes `rte_pktmbuf_mtod` for both src and dst.
> >
> > Bugzilla ID: 1269
> > Fixes: 623dc9364dc6 ("app/dma-perf: introduce DMA performance test")
> > Cc: cheng1.jiang@intel.com
> >
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
> > Suggested-by: Anoob Joseph <anoobj@marvell.com>
> > Suggested-by: Jerin Jacob <jerinj@marvell.com>
> >
> Acked-by: Huisong Li <lihuisong@huawei.com>
Adding some missing acks.
Applied, thanks.
next prev parent reply other threads:[~2023-11-14 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 7:18 [PATCH] app/dma-perf: fix physical address seg-fault Vipin Varghese
2023-08-16 7:26 ` [EXT] " Anoob Joseph
2023-08-16 7:31 ` Varghese, Vipin
2023-08-16 9:24 ` [PATCH v2] " Vipin Varghese
2023-08-16 9:35 ` Vipin Varghese
2023-08-16 9:42 ` Vipin Varghese
2023-08-16 10:12 ` Jerin Jacob
2023-08-16 10:46 ` [EXT] " Anoob Joseph
2023-09-21 2:28 ` Jiang, Cheng1
2023-10-04 9:00 ` Varghese, Vipin
2023-10-04 13:00 ` Jerin Jacob
2023-10-19 4:19 ` [PATCH v3] " Vipin Varghese
2023-10-24 2:16 ` lihuisong (C)
2023-11-14 14:27 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-19 4:16 Vipin Varghese
2023-10-19 7:13 ` fengchengwen
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=1958005.yKVeVyVuyW@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=cheng1.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=lihuisong@huawei.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.