Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] i40e pppoe rss
Date: Tue, 12 Oct 2021 12:28:25 -0700	[thread overview]
Message-ID: <55127ee0-e85c-9dba-4086-31516a843d27@intel.com> (raw)
In-Reply-To: <20211011222800.GA17234@kvack.org>

On 10/11/2021 3:28 PM, Benjamin LaHaise wrote:
> I have been trying to get RSS working for incoming PPPoE packets with the
> Linux i40e driver.  After loading the DDP .pkgo file for PPPoE using
> "ethtool -f enp43s0f0 ppp-oe-ol2tpv2.pkgo 100", packets still come in on a
> single queue.  Changing destination IP addresses or port numbers in UDP
> packets does not result in any change in the ingress queue.  Are the
> ethtool commands required to enable RSS with PPPoE documented anywhere?
> The only documentation seems to rely on test-pmd with DPDK, but I am using
> the native Linux drivers and XDP.

Hi Ben, this was a known issue on an older package version, and since 
you asked, we realized that the version on intel.com hasn't been updated 
in a long time, and so doesn't have the fix.

We are working to correct the internal issues that lead to this stale 
package being left there and not updated, and are grateful you pointed 
us to the issue!

Please keep an eye out for the intel.com download page to be updated 
with the latest PPPoE package. Once you have that, RSS should start 
working correctly after loading the newer package.

Thanks for your patience, I don't have a direct ETA on this, but I did 
start the ball rolling internally.

-Jesse

  reply	other threads:[~2021-10-12 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 22:28 [Intel-wired-lan] i40e pppoe rss Benjamin LaHaise
2021-10-12 19:28 ` Jesse Brandeburg [this message]
2021-10-14 19:52   ` Jesse Brandeburg
2021-10-14 20:25     ` Benjamin LaHaise

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=55127ee0-e85c-9dba-4086-31516a843d27@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