From: Iain Barker <iain.barker@oracle.com>
To: "Tomáš Jánský" <tomas.jansky@flowmon.com>, users@dpdk.org
Subject: Re: [dpdk-users] Outer VLAN stripping X710 NIC
Date: Tue, 12 Mar 2019 05:50:45 -0700 (PDT) [thread overview]
Message-ID: <62a6832d-6265-4e5f-a332-2513ef002680@default> (raw)
In-Reply-To: <CAPP7y6whcx3NCS3CBeLimYrx6s8bJ5O8ZOPsmATWqSi5k6UAVw@mail.gmail.com>
I posted my observations on the same issue a year or so ago...
See my follow-ups on this thread for a patch to work around the problem:
http://mails.dpdk.org/archives/users/2017-October/002530.html
Note that the patch has real-time overhead so was rejected.
But we are using it to good effect in our production systems.
next parent reply other threads:[~2019-03-12 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPP7y6whcx3NCS3CBeLimYrx6s8bJ5O8ZOPsmATWqSi5k6UAVw@mail.gmail.com>
2019-03-12 12:50 ` Iain Barker [this message]
2019-02-22 7:59 Tomáš Jánský
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=62a6832d-6265-4e5f-a332-2513ef002680@default \
--to=iain.barker@oracle.com \
--cc=tomas.jansky@flowmon.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).