DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Иванов Алексей" <ivalesh1@yandex.ru>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] QinQ and MPLS
Date: Thu, 5 Sep 2013 08:07:39 -0700	[thread overview]
Message-ID: <20130905080739.30d523b4@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <346711378362293@web22g.yandex.ru>

On Thu, 05 Sep 2013 10:24:53 +0400
Иванов Алексей <ivalesh1@yandex.ru> wrote:

> Hi to everyone!
> 
> A couple of questions about DPDK:
> 
> 1. Can Intel DPDK work with double tagged ethernet frames? To read frame with 2 tags and to write frame to the wire with two tags (QinQ technology)
> 
> 2. Can Intel DPDK read and write MPLS tags?
>  
> --
> Алексей

It reads/writes raw packets, what protocol you want to use is up to you.

  reply	other threads:[~2013-09-05 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  6:24 Иванов Алексей
2013-09-05 15:07 ` Stephen Hemminger [this message]
2013-09-12  9:14   ` Zhu, Heqing

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=20130905080739.30d523b4@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ivalesh1@yandex.ru \
    /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).