test suite reviews and discussions
 help / color / mirror / Atom feed
From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, lijuan.tu@intel.com, zhiminx.huang@intel.com
Subject: [DTS][PATCH V1 0/2] Updating packet module for new util functions and packet types.
Date: Tue,  4 Jul 2023 06:47:24 +0000	[thread overview]
Message-ID: <20230704064726.455361-1-ke1.xu@intel.com> (raw)

Packet module is designed to support packet organizing, analyzing and
 processing of different packet types. This patch introduced several
 new functions and supported new packet types in this module.

Added support for GTPU and GENEVE packet. Packet module only supports
 limited tunneling layers like VxLAN, GRE. New packet types are required
 in recent DPDK releases and GTPU and GENEVE are required to be added.

Added new util functions. Packet module introduced several util functions
 for writing packets into files, getting and increasing IP addresses,
 getting ether types and so on. As more packet types are introduced, some
 other util functions are required. This patch implemented a set of packet
 layer indexing, packet payload, segment and checksum checking. This patch
 also fixed some bad doc strings.

Ke Xu (2):
  framework/packet: Add GTPU and GENEVE support for packet module.
  framework/packet: Update packet module for new methods.

 framework/packet.py | 864 +++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 860 insertions(+), 4 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-07-04  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  6:47 Ke Xu [this message]
2023-07-04  6:47 ` [V1][DTS 1/2] framework/packet: Add GTPU and GENEVE support for packet module Ke Xu
2023-07-04  6:47 ` [V1][DTS 2/2] framework/packet: Update packet module for new methods Ke Xu

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=20230704064726.455361-1-ke1.xu@intel.com \
    --to=ke1.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=zhiminx.huang@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).