DPDK patches and discussions
 help / color / mirror / Atom feed
From: Oana Orjanu <oana.orjanu@keysight.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [dpdk] Header stripping
Date: Mon, 11 Mar 2019 08:23:48 +0000	[thread overview]
Message-ID: <MN2PR17MB2893067B40D3393ADF91F4F981480@MN2PR17MB2893.namprd17.prod.outlook.com> (raw)

Hello,

I’ve noticed that, when doing Ip reassembly or Ip fragmentation, the header of all functions that do this operation requires the packets to be already stripped of the Ethernet header when reaching it. What is the advantage of doing it like this, instead of handling the packet manipulation in those functions? Right now, it seems to me that anyone who wants to use these functionalities must know their traffic pattern precisely and explicitly strip off the Ethernet of vlan header before having reassembly and fragmentation work.


Regards,
Oana


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

                 reply	other threads:[~2019-03-11  8:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=MN2PR17MB2893067B40D3393ADF91F4F981480@MN2PR17MB2893.namprd17.prod.outlook.com \
    --to=oana.orjanu@keysight.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).