From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] nfp: add support for new metadata api
Date: Wed, 4 Jan 2017 14:48:03 +0000 [thread overview]
Message-ID: <67da8c13-f437-92f7-05fd-9ef441860757@intel.com> (raw)
In-Reply-To: <CAD+H990+t61m3Tc6Q4xi-pHB-O0ezonnQG15Qt50hWhke9A2=w@mail.gmail.com>
On 1/4/2017 2:43 PM, Alejandro Lucero wrote:
> Hi Ferruh,
>
> On Wed, Jan 4, 2017 at 3:15 PM, Ferruh Yigit <ferruh.yigit@intel.com
> <mailto:ferruh.yigit@intel.com>> wrote:
>
> On 12/20/2016 2:13 PM, Alejandro Lucero wrote:
> > NFP is a smart programmable NIC and firmware is deployed for specific
> > system needs, like offloading OVS, vRouter, contrack or eBPF into the
> > hardware. This often requires to give metadata to the host within
> > packets delivered. Last NFP firmware implementations support richer
> > metadata api facilitating interaction between firmware and host code.
> >
> > Old way of handling metadata needs to be still there for supporting
> > old firmware.
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com <mailto:alejandro.lucero@netronome.com>>
> > ---
>
> <...>
>
> > +
> > + } else if (NFP_DESC_META_LEN(rxd)) {
> > + meta_offset = (uint8_t *)mbuf->buf_addr;
> > + meta_info = rte_be_to_cpu_32(*(uint32_t *)meta_offset);
> > + meta_offset += 4;
> > + /* NFP PMD just supports metadata for hashing */
> > + switch (meta_info & NFP_NET_META_FIELD_MASK) {
> > + case NFP_NET_META_HASH:
> > + meta_info >>= NFP_NET_META_FIELD_SIZE;
> > + hash = rte_be_to_cpu_32(*(uint32_t *)meta_offset);
> > + hash_type = meta_info && NFP_NET_META_FIELD_MASK;
>
> I already applied this patch but above "&&" looks wrong.
> Most probably intention is "bitwise AND" (&), do you want me fix this as
> "&" or remove the patch completely to replace with new version?
>
>
> Yes, that is wrong. I wonder how related tests did not fail. I'll check
> that right now.
>
> Maybe it is better to wait for another patch version or at least to be
> sure that simple change is good enough.
> Let me to peer into those tests and re-run them with that fix applied.
Removed from next-net, patchwork status updated as "Change Requested".
>
>
> Thanks,
> ferruh
>
>
prev parent reply other threads:[~2017-01-04 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 14:13 Alejandro Lucero
2017-01-04 12:26 ` Ferruh Yigit
2017-01-04 14:15 ` Ferruh Yigit
2017-01-04 14:43 ` Alejandro Lucero
2017-01-04 14:48 ` Ferruh Yigit [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=67da8c13-f437-92f7-05fd-9ef441860757@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.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).