From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: "Moran, John" <John.Moran@viasat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel XL710
Date: Fri, 12 Jun 2015 02:32:17 +0000 [thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC0576C87D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <6ABAE239154E5C46B731F83C9877C5EAF3EA88CD@wdc1exchmbxp02.hq.corp.viasat.com>
The header split support is being planned in next DPDK release.
If you can implement it and submit a patch before next release, it is welcomed. Thanks
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Moran, John
> Sent: Wednesday, June 10, 2015 11:07 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Intel XL710
>
> Hello,
>
> I submitted this question yesterday, when I did not belong to group. Re-
> submitting now that I am a member!
>
> I am working on a design where a dpdk/intel710 based switch will receive
> VXLAN traffic (DPDK 2.0 with centos 7 and kvm).
> Ideally we would like to have the NIC strip the VXLAN header and then
> forward the packet based on mac or vlan id of the inner packet.
>
> Question. From looking the Add a VXLAN sample at
> //www.litchfie.dpdk.org/ml/archives/dev/2015-April/016518.html. it looks
> as if is possible to use the HW header splitter to access inner vlan. The NIC
> will then assign the packet to the correct internal queue?
>
> I just want to confirm this before I start make promises in design.
>
> Thanks for any help,
>
> Jack Moran
> ViaSat
prev parent reply other threads:[~2015-06-12 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 15:06 Moran, John
2015-06-12 2:32 ` Liu, Jijiang [this message]
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=1ED644BD7E0A5F4091CF203DAFB8E4CC0576C87D@SHSMSX101.ccr.corp.intel.com \
--to=jijiang.liu@intel.com \
--cc=John.Moran@viasat.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).