From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Ravi Kumar <Ravi1.kumar@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v1] crypto/ccp: use contiguous allocation for DMA memory
Date: Tue, 17 Apr 2018 13:02:58 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CCD626F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1523961144-79110-1-git-send-email-Ravi1.kumar@amd.com>
> -----Original Message-----
> From: Ravi Kumar [mailto:Ravi1.kumar@amd.com]
> Sent: Tuesday, April 17, 2018 11:32 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> hemant.agrawal@nxp.com
> Subject: [PATCH v1] crypto/ccp: use contiguous allocation for DMA memory
>
> rte_eal_get_physmem_layout() is obsolete now.
> This patch fix the broken API usage and allocates DMA memory with
> RTE_MEMZONE_IOVA_CONTIG memzone flag.
>
> Signed-off-by: Ravi Kumar <Ravi1.kumar@amd.com>
Squashed into second commit of the AMD CCP patchset and applied to dpdk-next-crypto.
Thanks for the quick patch!
Pablo
prev parent reply other threads:[~2018-04-17 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:32 Ravi Kumar
2018-04-17 10:35 ` Burakov, Anatoly
2018-04-17 13:02 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8976CCD626F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=Ravi1.kumar@amd.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).