From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] 710/i40e, RSS and 802.1ad (double vlan)
Date: Mon, 22 Nov 2021 18:04:03 -0800 [thread overview]
Message-ID: <65909259-6de3-e595-bbe8-f07693c66543@intel.com> (raw)
In-Reply-To: <20210211174937.00006632@intel.com>
On 2/11/2021 5:49 PM, Jesse Brandeburg wrote:
> Dan Siemon wrote:
>
>> On Tue, 2021-02-09 at 12:02 -0800, Jesse Brandeburg wrote:
>>> Please provide us with which driver/kernel/firmware you're running,
>>> uname -a
>>> ethtool -i ethx
>>> lspci -vvv -s < your pci bus:dev.fn>
>>
>> We are ok to update to the latest 710 firmware and we follow the kernel
>> releases closely.
>>
>> As we haven't had problems related to firmware, we still have many 710s
>> in the field that are on 6.01 firmware. Below are dumps from a couple
>> of our test boxes where I have upgraded the firmware.
>
> Hi Dan, thanks for the detail, I think your firmware is new enough, but
> I'm pretty sure our driver isn't configuring enough (it's currently an
> unsupported feature in Linux i40e) to get it working. Newer than 6.01 is
> all I know of that is required for firmware based on what I know right
> now.
>
> I've filed an internal issue tracker against i40e and sometime
> (hopefully) soon we'll have the team looking into details. I don't have
> any timeline for you currently, sorry.
>
> I agree this is an important use case. We appreciate your reporting the
> issue to us. Based on what I found when doing some initial triage, it
> doesn't seem like a simple fix in the code, so I can't offer you a
> patch to fix the issue like I wish I could.
>
> Please keep us posted if you find any other relevant details, and I'll
> try to update this thread if we find any info or get a test patch up
> and running.
An update to this old thread:
The current i40e out-of-tree driver from intel.com/e1000.sf.net has
support for a limited use case of double vlan for virtual machines (VFs)
but the interface used is customer specific and not upstream (it's in
sysfs).
In the meantime, I guess your best bet is DPDK. Currently an
implementation for the upstream kernel is not available and I don't know
when it will become so.
Thanks for your patience on this one, I'm working with the team to make
sure we don't create feature gaps like this between out-of-tree and
upstream in the future. I appreciate that you brought this to our attention.
Thanks,
Jesse
prev parent reply other threads:[~2021-11-23 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 3:37 [Intel-wired-lan] 710/i40e, RSS and 802.1ad (double vlan) dan
2021-02-07 2:24 ` Brandeburg, Jesse
[not found] ` <8c7d255047890290948cf51450b1f860e013b48c.camel@coverfire.com>
2021-02-09 15:03 ` Dan Siemon
2021-02-09 20:02 ` Jesse Brandeburg
2021-02-09 20:59 ` Dan Siemon
2021-02-12 1:49 ` Jesse Brandeburg
2021-11-23 2:04 ` Jesse Brandeburg [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=65909259-6de3-e595-bbe8-f07693c66543@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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