From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] examples/dpdk_qat: Fix reference to old mbuf field "data"
Date: Thu, 20 Nov 2014 10:50:07 +0000 [thread overview]
Message-ID: <1416480607-5198-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
DPDK QAT app was using the old "data" field in mbuf,
so it has been subtituted with rte_pktmbuf_mtod function.
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
examples/dpdk_qat/crypto.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/examples/dpdk_qat/crypto.c b/examples/dpdk_qat/crypto.c
index 318d47c..f49408a 100644
--- a/examples/dpdk_qat/crypto.c
+++ b/examples/dpdk_qat/crypto.c
@@ -183,7 +183,7 @@ struct glob_keys g_crypto_hash_keys = {
*
*/
#define PACKET_DATA_START_PHYS(p) \
- ((p)->buf_physaddr + ((char *)p->data - (char *)p->buf_addr))
+ ((p)->buf_physaddr + (p)->data_off)
/*
* A fixed offset to where the crypto is to be performed, which is the first
@@ -773,7 +773,7 @@ enum crypto_result
crypto_encrypt(struct rte_mbuf *rte_buff, enum cipher_alg c, enum hash_alg h)
{
CpaCySymDpOpData *opData =
- (CpaCySymDpOpData *) ((char *) (rte_buff->data)
+ (CpaCySymDpOpData *) (rte_pktmbuf_mtod(rte_buff, char *)
+ CRYPTO_OFFSET_TO_OPDATA);
uint32_t lcore_id;
@@ -848,7 +848,7 @@ enum crypto_result
crypto_decrypt(struct rte_mbuf *rte_buff, enum cipher_alg c, enum hash_alg h)
{
- CpaCySymDpOpData *opData = (void*) (((char *) rte_buff->data)
+ CpaCySymDpOpData *opData = (void*) (rte_pktmbuf_mtod(rte_buff, char *)
+ CRYPTO_OFFSET_TO_OPDATA);
uint32_t lcore_id;
--
1.7.4.1
next reply other threads:[~2014-11-20 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 10:50 Pablo de Lara [this message]
2014-11-24 15:50 ` Thomas Monjalon
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=1416480607-5198-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
/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).