All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Helin Zhang <helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [RFC 01/17] mbuf: add definitions of unified packet types
Date: Mon, 19 Jan 2015 11:33:06 -0500	[thread overview]
Message-ID: <20150119163306.GD21790@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1421637803-17034-2-git-send-email-helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

On Mon, Jan 19, 2015 at 11:23:07AM +0800, Helin Zhang wrote:
> As there are only 6 bit flags in ol_flags for indicating packet types,
> which is not enough to describe all the possible packet types hardware
> can recognize. For example, i40e hardware can recognize more than 150
> packet types. Unified packet type is composed of tunnel type, L3 type,
> L4 type and inner L3 type fields, and can be stored in 16 bits mbuf
> field of 'packet_type'.
> 
> Signed-off-by: Helin Zhang <helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Cunming Liang <cunming.liang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Jijiang Liu <jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
>  lib/librte_mbuf/rte_mbuf.h | 68 ++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 68 insertions(+)
> 
> diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
> index 16059c6..94eb38f 100644
> --- a/lib/librte_mbuf/rte_mbuf.h
> +++ b/lib/librte_mbuf/rte_mbuf.h
> @@ -165,6 +165,74 @@ extern "C" {
>  /* Use final bit of flags to indicate a control mbuf */
>  #define CTRL_MBUF_FLAG       (1ULL << 63) /**< Mbuf contains control data */
>  
> +/*
> + * Sixteen bits are divided into several fields to mark packet types. Note that
> + * each field is indexical.
> + * - Bit 3:0 is for tunnel types.
> + * - Bit 7:4 is for L3 or outer L3 (for tunneling case) types.
> + * - Bit 10:8 is for L4 types. It can also be used for inner L4 types for
> + *   tunneling packets.
This seems a bit sparse, in that the protocol field is 8 bits wide in a packet.
There are several common protocls that you don't have listed, and you've already
exhausted your namespace with the list you have.
Neil

  parent reply	other threads:[~2015-01-19 16:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19  3:23 [RFC 00/17] unified packet type Helin Zhang
     [not found] ` <1421637803-17034-1-git-send-email-helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-01-19  3:23   ` [RFC 01/17] mbuf: add definitions of unified packet types Helin Zhang
     [not found]     ` <1421637803-17034-2-git-send-email-helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-01-19 16:19       ` Ananyev, Konstantin
     [not found]         ` <2601191342CEEE43887BDE71AB977258213DDE25-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-20  3:47           ` Zhang, Helin
2015-01-19 16:33       ` Neil Horman [this message]
     [not found]         ` <20150119163306.GD21790-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-01-19 17:27           ` Olivier MATZ
     [not found]             ` <54BD3E66.3040709-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2015-01-19 18:15               ` Neil Horman
2015-01-20  2:28               ` Zhang, Helin
     [not found]                 ` <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7EB2A1-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-20  9:53                   ` Olivier MATZ
2015-01-19  3:23   ` [RFC 02/17] e1000: support of unified packet type Helin Zhang
2015-01-19  3:23   ` [RFC 03/17] ixgbe: " Helin Zhang
2015-01-19  3:23   ` [RFC 04/17] " Helin Zhang
2015-01-19  3:23   ` [RFC 05/17] i40e: " Helin Zhang
2015-01-19  3:23   ` [RFC 06/17] bond: " Helin Zhang
2015-01-19  3:23   ` [RFC 07/17] enic: " Helin Zhang
2015-01-19  3:23   ` [RFC 08/17] vmxnet3: " Helin Zhang
2015-01-19  3:23   ` [RFC 09/17] app/test-pipeline: " Helin Zhang
2015-01-19  3:23   ` [RFC 10/17] app/test-pmd: " Helin Zhang
2015-01-19  3:23   ` [RFC 11/17] app/test: " Helin Zhang
2015-01-19  3:23   ` [RFC 12/17] examples/ip_fragmentation: " Helin Zhang
2015-01-19  3:23   ` [RFC 13/17] examples/ip_reassembly: " Helin Zhang
2015-01-19  3:23   ` [RFC 14/17] examples/l3fwd-acl: " Helin Zhang
2015-01-19  3:23   ` [RFC 15/17] examples/l3fwd-power: " Helin Zhang
2015-01-19  3:23   ` [RFC 16/17] examples/l3fwd: " Helin Zhang
2015-01-19  3:23   ` [RFC 17/17] mbuf: remove old packet type bit masks for ol_flags Helin Zhang

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=20150119163306.GD21790@hmsreliant.think-freely.org \
    --to=nhorman-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=helin.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.