From: "Morten Brørup" <mb@smartsharesystems.com>
To: <longtb5@viettel.com.vn>, <roszenrami@gmail.com>,
"Olivier Matz" <olivier.matz@6wind.com>
Cc: <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
<thomas@monjalon.net>,
"Varghese, Vipin" <vipin.varghese@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>, <arybchenko@solarflare.com>,
<ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [RFC] function to parse packet headers
Date: Thu, 10 Jan 2019 09:21:13 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B425BB@smartserver.smartshare.dk> (raw)
In-Reply-To: <000001d4a895$85ffbbf0$91ff33d0$@viettel.com.vn>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of
> longtb5@viettel.com.vn
>
> Also for the bulk API, another option would be passing in a `uint64_t
> malformed_mask` and let the bulk function set the correspond bit (1 <<
> pos) of that mask if the packet at position pos is malformed.
>
> void rte_hdr_parse_bulk(struct rte_mbuf **pkts, uint64_t
> *malformed_mask, uint_fast16_t nb_pkts);
>
> The packet mask idea is used extensively in the packet framework
> (rte_pipeline, rte_port, rte_table).
>
A key property of the bulk function is to make it easy passing on the resulting array of non-malformed packets to the next bulk function, e.g. GRO. A malformed_mask would require an intermediate step of processing before the resulting array can be passed on.
For functions like GRO, either the MBUF must contain a valid/malformed indication, or the array provided to them must contain only valid packets.
Med venlig hilsen / kind regards
- Morten Brørup
next prev parent reply other threads:[~2019-01-10 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 3:43 longtb5
2019-01-09 15:38 ` Morten Brørup
2019-01-10 3:25 ` longtb5
2019-01-10 8:21 ` Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-08 16:48 Morten Brørup
2019-01-08 20:09 ` Rami Rosen
2019-01-09 15:53 ` Morten Brørup
2019-01-09 23:57 ` Thomas Monjalon
2019-01-10 1:03 ` Rami Rosen
2019-01-11 0:11 ` Stephen Hemminger
2019-01-11 7:56 ` Andrew Rybchenko
2019-01-11 8:16 ` Morten Brørup
2019-01-11 8:28 ` Andrew Rybchenko
2019-01-11 8:35 ` Olivier Matz
2019-01-11 9:49 ` Ananyev, Konstantin
2019-01-11 12:04 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35B425BB@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=longtb5@viettel.com.vn \
--cc=olivier.matz@6wind.com \
--cc=roszenrami@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=vipin.varghese@intel.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).