From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Hayato Momma <h-momma@ce.jp.nec.com>
Subject: Re: [dpdk-dev] [memnic PATCH 3/7] pmd: use helper macros
Date: Thu, 25 Sep 2014 00:01:20 +0000 [thread overview]
Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD02AD9E6D@BPXM14GP.gisp.nec.co.jp> (raw)
In-Reply-To: <2846511.VthLZyxgb4@xps13>
> Subject: Re: [dpdk-dev] [memnic PATCH 3/7] pmd: use helper macros
>
> 2014-09-11 07:47, Hiroshi Shimamoto:
> > Do not touch pktmbuf directly.
> >
> > Instead of direct access, use rte_pktmbuf_pkt_len() and rte_pktmbuf_data_len()
> > to access the property.
>
> I guess this change is for compatibility with DPDK 1.8.
Yep, I had the thought need to prepare upcoming code.
> Does it have an impact on performance?
No, it must not.
thanks,
Hiroshi
>
> --
> Thomas
prev parent reply other threads:[~2014-09-24 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 7:47 Hiroshi Shimamoto
2014-09-24 15:14 ` Thomas Monjalon
2014-09-25 0:01 ` Hiroshi Shimamoto [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=7F861DC0615E0C47A872E6F3C5FCDDBD02AD9E6D@BPXM14GP.gisp.nec.co.jp \
--to=h-shimamoto@ct.jp.nec.com \
--cc=dev@dpdk.org \
--cc=h-momma@ce.jp.nec.com \
--cc=thomas.monjalon@6wind.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).