DPDK usage discussions
 help / color / mirror / Atom feed
From: Jim Murphy <jmurphy@arista.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] How to configure an Ethernet Driver to ignore the Ethertype
Date: Wed, 26 Feb 2020 15:53:20 -0800	[thread overview]
Message-ID: <CAJC5fi3K=6rRtK40eubpav4FDTqeOWJRRAooZQpFfrSNp1sq0Q@mail.gmail.com> (raw)
In-Reply-To: <71565765-d37d-814f-a509-db810fbb36b0@linux.vnet.ibm.com>

Hi,

Thanks for the pointers on higig I will look into it. However in this case
these headers are defined arbitrarily using p4.

Thanks,

Jim

On Wed, Feb 26, 2020, 1:58 PM David Christensen <drc@linux.vnet.ibm.com>
wrote:

> > I was wondering if there is a way to get the Ethernet driver to ignore
> the
> > Ethertype. The problem I am having is that I am dealing with a switch
> chip
> > that is redirecting packets to the processor via an offload ethernet
> > device. Before offload the switch chip adds a header that pushes the DA
> > into the spot where the EtherType is normally. As a result, the ethertype
> > is essentially a random value so some packets will look like that have a
> > snap header and the driver will conclude that the packet is corrupted I
> > presume. I am working with the IXGBE driver.
>
> Are you talking about HiGig/HiGig2 headers? I think your support in the
> DPDK will be limited to octeontx2 (look for switch_header="higig2" in
> https://fast.dpdk.org/doc/pdf-guides/nics-master.pdf).
>
> Dave
>

      reply	other threads:[~2020-02-26 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 19:19 Jim Murphy
2020-02-26 21:58 ` David Christensen
2020-02-26 23:53   ` Jim Murphy [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='CAJC5fi3K=6rRtK40eubpav4FDTqeOWJRRAooZQpFfrSNp1sq0Q@mail.gmail.com' \
    --to=jmurphy@arista.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=users@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).