From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/3] app/testpmd: code refactory for macswap
Date: Tue, 11 Dec 2018 04:02:52 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611532FC707@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <c4d459cf-5bac-19b4-c1f2-cb849b6e1e4e@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, December 11, 2018 1:44 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Wiles, Keith <keith.wiles@intel.com>; Ananyev,
> Konstantin <konstantin.ananyev@intel.com>
> Cc: dev@dpdk.org; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>; Yongseok Koh <yskoh@mellanox.com>
> Subject: Re: [dpdk-dev] [PATCH v2 1/3] app/testpmd: code refactory for
> macswap
>
> On 11/22/2018 5:38 PM, Qi Zhang wrote:
> > Move macswap workload to dedicate function, so we can further enable
> > platform specific optimized version.
> >
> > Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
>
> <...>
>
> > @@ -0,0 +1,40 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright(c) 2018 Intel Corporation */
> > +
> > +#ifndef _L2FWD_H_
> > +#define _L2FWD_H_
>
> Looks like copy-paste artifact, there are a few more in patchset.
>
> <...>
>
> > @@ -0,0 +1,36 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright(c) 2018 Intel Corporation */
> > +
> > +#ifndef _L2FWD_COMMON_H_
> > +#define _L2FWD_COMMON_H_
> > +
> > +static inline uint64_t
> > +ol_flags_init(uint64_t tx_offload)
> > +{
> > + uint64_t ol_flags = 0;
> > +
> > + ol_flags |= (tx_offload & DEV_TX_OFFLOAD_VLAN_INSERT) ?
> > + PKT_TX_VLAN_PKT : 0;
>
> 'PKT_TX_VLAN_PKT' is depreciated and replaced with 'PKT_TX_VLAN'. I think it
> is better to keep as it is in this patch, since mainly it copies from one place to
> another, but can you update this in new patch in this patchset?
Ok, I will replace.
>
> > + ol_flags |= (tx_offload & DEV_TX_OFFLOAD_QINQ_INSERT) ?
> > + PKT_TX_QINQ_PKT : 0;
>
> Same here, 'PKT_TX_QINQ_PKT' replaced with 'PKT_TX_QINQ'.
>
> > + ol_flags |= (tx_offload & DEV_TX_OFFLOAD_MACSEC_INSERT) ?
> > + PKT_TX_MACSEC : 0;
> > +
> > + return ol_flags;
> > +}
> > +
> > +static inline void
> > +mbuf_field_set(struct rte_mbuf *mb, uint64_t ol_flags,
> > + uint16_t vlan, uint16_t vlan_outer) {
> > + mb->ol_flags &= IND_ATTACHED_MBUF | EXT_ATTACHED_MBUF;
>
> I guess above line is to prevent those bits overwritten, but with '|='
> assignment below I think they will be preserved already, do we need above line?
> cc'ed Yongseok.
I think above line also clean up other bits besides IND_ATTACHED_MBUF | EXT_ATTACHED_MBUF
But I don't know if it is necessary, so I just keep it the same way as before.
>
> > + mb->ol_flags |= ol_flags;
> > + mb->l2_len = sizeof(struct ether_hdr);
> > + mb->l3_len = sizeof(struct ipv4_hdr);
> > + mb->vlan_tci = vlan;
> > + mb->vlan_tci_outer = vlan_outer;
>
> Setting 'vlan_tci' or 'vlan_tci_outer' makes sense only if 'PKT_TX_VLAN' and
> 'PKT_TX_QINQ' set, since there is already an check for them above, does it
> make sense to do these assignment in them, for better performance.
Good point, we can skip these memory write if PKT_TX_VLAN and PKT_TX_QINQ is not set.
Thanks
Qi
next prev parent reply other threads:[~2018-12-11 4:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 17:26 [dpdk-dev] [PATCH 0/3] improve MAC swap performance Qi Zhang
2018-11-22 17:26 ` [dpdk-dev] [PATCH 1/3] app/testpmd: code refactory for macswap Qi Zhang
2018-11-22 17:26 ` [dpdk-dev] [PATCH 2/3] app/testpmd: improve MAC swap performance for x86 Qi Zhang
2018-11-22 17:26 ` [dpdk-dev] [PATCH 3/3] app/testpmd: further " Qi Zhang
2018-11-22 17:38 ` [dpdk-dev] [PATCH v2 0/3] improve MAC swap performance Qi Zhang
2018-11-22 17:38 ` [dpdk-dev] [PATCH v2 1/3] app/testpmd: code refactory for macswap Qi Zhang
2018-12-10 17:44 ` Ferruh Yigit
2018-12-11 4:02 ` Zhang, Qi Z [this message]
2018-11-22 17:38 ` [dpdk-dev] [PATCH v2 2/3] app/testpmd: improve MAC swap performance for x86 Qi Zhang
2018-12-10 17:44 ` Ferruh Yigit
2018-11-22 17:38 ` [dpdk-dev] [PATCH v2 3/3] app/testpmd: further " Qi Zhang
2018-12-11 5:55 ` [dpdk-dev] [PATCH v2 0/3] improve MAC swap performance Qi Zhang
2018-12-11 5:55 ` [dpdk-dev] [PATCH v2 1/3] app/testpmd: code refactory for macswap Qi Zhang
2018-12-11 15:48 ` Ferruh Yigit
2018-12-14 11:14 ` Iremonger, Bernard
2018-12-14 11:21 ` Zhang, Qi Z
2018-12-11 5:55 ` [dpdk-dev] [PATCH v2 2/3] app/testpmd: improve MAC swap performance for x86 Qi Zhang
2018-12-13 19:50 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2018-12-14 11:21 ` [dpdk-dev] " Iremonger, Bernard
2018-12-14 11:36 ` Zhang, Qi Z
2018-12-11 5:55 ` [dpdk-dev] [PATCH v2 3/3] app/testpmd: further " Qi Zhang
2018-12-16 0:58 ` [dpdk-dev] [PATCH v3 0/3] improve MAC swap performance Qi Zhang
2018-12-16 0:58 ` [dpdk-dev] [PATCH v3 1/3] app/testpmd: code refactory for macswap Qi Zhang
2018-12-18 11:06 ` Iremonger, Bernard
2018-12-16 0:58 ` [dpdk-dev] [PATCH v3 2/3] app/testpmd: improve MAC swap performance for x86 Qi Zhang
2018-12-18 11:07 ` Iremonger, Bernard
2018-12-16 0:58 ` [dpdk-dev] [PATCH v3 3/3] app/testpmd: further " Qi Zhang
2018-12-18 11:09 ` Iremonger, Bernard
2018-12-18 0:15 ` [dpdk-dev] [PATCH v3 0/3] improve MAC swap performance Ferruh Yigit
2018-12-18 16:29 ` Ferruh Yigit
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=039ED4275CED7440929022BC67E70611532FC707@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yskoh@mellanox.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).